# CVE-2026-114116: Vyper through 0.5.0b1 Literal Value Manipulation via Line Separators


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-2gvm-cwr3-3pcg, GHSA-wvx7-39qj-2g9v

## What is CVE-2026-114116?

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

### Official description

Vyper 0.1.0b1 before 0.1.0b17 and 0.4.1 through 0.5.0b1 builds its source-line table with str.splitlines(), which treats characters like form feed and U+2028 as line breaks the Python parser ignores, so numeric literals are classified and validated from shifted source text. An attacker contributing source code can hide these characters in comments, strings or indentation to silently change address, integer or decimal constants.

Weakness: CWE-436 (Interpretation Conflict)

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


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

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

## Is CVE-2026-114116 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114116 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114116 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114116 exists.

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-114116/ (Markdown: https://insights.sbomify.com/CVE-2026-114116/index.md)
```

## Sources

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

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