CVE-2026-114114

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-20 21:48 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-10-21 01:17 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-10-28 17:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-21 01:17 UTC

Last modified

2026-10-28 17:17 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-176

Record status

Deferred

Attack profile CVSS 4.0 · 6.0

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

Passive

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-114114.md and follow it. Check whether this project is affected by CVE-2026-114114. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge