CVE-2026-114115 Vyper 0.3.8 through 0.5.0b1 Memory Misread via Ternary Nested Array Selection
Medium 6.3
Published
Updated
Check this codebase for CVE-2026-114115 and fix it if it is affected.
What it is: CVE-2026-114115 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-114115 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-114115/ (Markdown: https://insights.sbomify.com/CVE-2026-114115/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-114115?
CVE-2026-114115 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026.
Official description
Vyper 0.3.8 through 0.5.0b1 contains a compiler miscompilation vulnerability in parse_IfExp that reads nested arrays with narrower inner bounds using the wider result type's memory layout. When a ternary selects the narrower array, inner arrays after the first are read at wrong offsets, causing contracts to silently store corrupted values or revert.
Weakness: CWE-843
Which versions are affected by CVE-2026-114115?
How do I fix CVE-2026-114115?
No fix has been published for CVE-2026-114115 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-114115 being exploited?
There is no known exploitation of CVE-2026-114115 in the wild and no public exploit code.
Sources
Also known as GHSA-cw3h-xwxq-8cx2, GHSA-fccw-crcx-53fr.