# CVE-2026-114114: Vyper through 0.5.0b1 Literal Value Substitution via Multi-byte Characters


- **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-r3c7-7xwm-6vfw, GHSA-vchg-h45q-h36m

## What is CVE-2026-114114?

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

### Official description

Vyper 0.1.0b1 before 0.1.0b12, 0.1.0b14, and 0.4.1 through 0.5.0b1 mix character-based line offsets with Python's UTF-8 byte col_offset values in vyper/ast/parse.py, so multi-byte characters shift the source slices used to reconstruct later numeric literals. An attacker contributing source with non-ASCII identifiers that NFKC-normalize to ASCII, or an invisible byte-order mark, can silently substitute addresses, integers or other constants in compiled code.

Weakness: CWE-176 (Improper Handling of Unicode Encoding)

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


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

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

## Is CVE-2026-114114 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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