Incorrect contract behavior via skipped concat side effects
Published May 15, 2025 · Updated May 15, 2025
Incorrect code generation in Vyper 0.4.2rc1 and earlier allows attackers to trigger contracts that omit intended side effects. The concat() code-generation fast path ignores an argument whenever its maximum length is zero, so the argument expression is never evaluated. Triggering the affected bytecode requires a contract compiled from a zero-length bytestring ternary expression with a side effect; calls to that contract can silently omit intended state changes.
Summary
What happened
Incorrect code generation in Vyper 0.4.2rc1 and earlier allows attackers to trigger contracts that omit intended side effects. The concat() code-generation fast path ignores an argument whenever its maximum length is zero, so the argument expression is never evaluated. Triggering the affected bytecode requires a contract compiled from a zero-length bytestring ternary expression with a side effect; calls to that contract can silently omit intended state changes.
The record
- CVE
- CVE-2025-47285
- Published
- May 15, 2025
- Updated
- May 15, 2025
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-691
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 15, 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.2rc1
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 concat() side-effect 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