Vyperlang Vyper 0.3.10 for Python
Approved changes feed: RSS · Atom
cpe:2.3:a:vyperlang:vyper:0.3.10:*:*:*:*:python:*:*part: a version: 0.3.10 update: *
| Vendor | Vyperlang (dc52d44e-854a-52f8-9052-e8571d6475c7) |
|---|---|
| Product | Vyper (e8eea31d-2a87-5a71-9899-89db24052b75) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | python |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/vyperlang/vyper |
purl2cpe | 2026-06-01 10:16:19.979624 |
pkg:github/vyperlang/vyper |
purl2cpe | 2026-06-01 10:16:19.979625 |
pkg:pypi/vyper |
purl2cpe | 2026-06-01 10:16:19.979627 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-24559 |
vulnerable | 2026-06-08 06:29:41.481818 |
Vyper SHA3 code generation bug
LOW (3.7)
Vyper is a Pythonic Smart Contract Language for the EVM. There is an error in the stack management when compiling the `IR` for `sha3_64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand (that is, it cannot be triggered from regular vyper code). `sha3_64` is used for retrieval in mappings. No flow that would cache the `key` was found so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of vyper code so the impact is low. At the time of publication there is no patch available.
Published: 2024-02-05T21:04:42.056Z
Updated: 2024-08-26T18:13:59.422Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.