CVE-2026-114114: Vyper through 0.5.0b1 Literal Value Substitution via Multi-byte Characters
vyperlang · vyper
Fixed in 0.1.0b12 · Affected: vyperlang before 0.1.0b12 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 17% of scored CVEs
DescriptionCVE.org
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.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- vyperlang · vyperfrom 0.1.0b1 before 0.1.0b12
- vyperlang · vyperfrom 0.1.0b14 before 0.1.0b15
- vyperlang · vyperfrom 0.4.1 up to and including 0.5.0b1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- vyperlang
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-114114 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.