CVE-2026-114118 Details
Description
Vyper 0.3.4 through 0.5.0b1 computes the remaining blueprint size in create_from_blueprint by uint256 subtraction without first checking that code_offset is below the blueprint's code size, so a huge offset wraps to a small positive value. An attacker controlling code_offset can make a factory deploy contracts with no runtime code, potentially trapping ETH and tokens.
A vulnerability exists in Vyper versions 0.3.4 through 0.5.0b1 within the 'create_from_blueprint' function. The issue arises because the function calculates the remaining blueprint size using unsigned integer subtraction without first verifying that the 'code_offset' is less than the blueprint's total code size. This oversight allows a large offset to wrap around and result in a small positive value. An attacker who manipulates the 'code_offset' can exploit this flaw, causing a factory to deploy contracts that lack runtime code, which could lead to the loss of ETH and tokens.
Users can validate that 'code_offset' is less than 'extcodesize(target)' using an unsigned comparison before performing the subtraction. As a workaround, a fixed, valid offset can be used, or this bound can be explicitly enforced before calling 'create_from_blueprint'.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 21, 2026CISA-ADP
Assessed Oct 27, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-681 | Incorrect Conversion between Numeric Types | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Vyper | >= 0.3.4, <= 0.5.0b1 |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 27, 2026 | CVE Modified | CISA-ADP |
| Oct 21, 2026 | New CVE Received | [email protected] |
Volerion