Approved changes feed: RSS · Atom
cpe:2.3:a:vyperlang:vyper:*:-:*:*:*:python:*:*part: a version: * 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 purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/vyperlang/vyper |
purl2cpe | 2026-06-01 10:16:19.999311 |
pkg:github/vyperlang/vyper |
purl2cpe | 2026-06-01 10:16:19.999313 |
pkg:pypi/vyper |
purl2cpe | 2026-06-01 10:16:19.999314 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-21607 |
vulnerable | 2026-06-08 07:08:57.027238 |
Success of Certain Precompile Calls not Checked in Vyper
Vyper is a Pythonic Smart Contract Language for the EVM. When the Vyper Compiler uses the precompiles EcRecover (0x1) and Identity (0x4), the success flag of the call is not checked. As a consequence an attacker can provide a specific amount of gas to make these calls fail but let the overall execution continue. Then the execution result can be incorrect. Based on EVM's rules, after the failed precompile the remaining code has only 1/64 of the pre-call-gas left (as 63/64 were forwarded and spent). Hence, only fairly simple executions can follow the failed precompile calls. Therefore, we found no significantly impacted real-world contracts. None the less an advisory has been made out of an abundance of caution. This issue is fixed in 0.4.1.
Published: 2025-01-14T17:32:58.169Z
Updated: 2025-04-24T14:39:51.551Z |
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.