Incorrect contract execution via unchecked precompile results
Published Jan 14, 2025 · Updated Apr 24, 2025
Incorrect contract execution in Vyper before 0.4.1 allows remote authenticated users to produce wrong results via gas-limited calls. The compiler emits EcRecover and Identity staticcalls without asserting their success flag, so execution continues with stale or empty output after an out-of-gas failure. Exploitation requires carefully chosen gas that lets the precompile fail while leaving simple later code executable; the project found no significantly impacted real-world contracts.
Summary
What happened
Incorrect contract execution in Vyper before 0.4.1 allows remote authenticated users to produce wrong results via gas-limited calls. The compiler emits EcRecover and Identity staticcalls without asserting their success flag, so execution continues with stale or empty output after an out-of-gas failure. Exploitation requires carefully chosen gas that lets the precompile fail while leaving simple later code executable; the project found no significantly impacted real-world contracts.
The record
- CVE
- CVE-2025-21607
- Published
- Jan 14, 2025
- Updated
- Apr 24, 2025
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-670
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Apr 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream gas-limited precompile proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo