# CVE-2026-114118: Vyper 0.3.4 through 0.5.0b1 create_from_blueprint Offset Validation Bypass via Unsigned Wraparound


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-fxg7-4wqg-c8gh, GHSA-p4mc-qjvf-mf2m

## What is CVE-2026-114118?

CVE-2026-114118 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026. 

### Official 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.

Weakness: CWE-681 (Incorrect Conversion between Numeric Types)

## Which versions are affected by CVE-2026-114118?


## How do I fix CVE-2026-114118?

No fix has been published for CVE-2026-114118 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114118 being exploited?

There is no known exploitation of CVE-2026-114118 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114118 and fix it if it is affected.

What it is: CVE-2026-114118 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114118 in the wild and no public exploit code.

Affected product: vyperlang vyper. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114118/ (Markdown: https://insights.sbomify.com/CVE-2026-114118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114118
- OSV: https://osv.dev/vulnerability/CVE-2026-114118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114118/
Summaries are generated and may contain mistakes; the official description above is the record.