cve.bz

CVE-2026-114114 vyperlang vyper: Improper Handling of Unicode Encoding

6.0 mediumEPSS 0.3%

Medium (6.0) in vyperlang vyper. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.0 medium
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

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-176 Improper Handling of Unicode Encoding
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-114114 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114114?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114114?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114114 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
vyperlang vyperfrom 0.1.0b1 before 0.1.0b12
vyperlang vyperfrom 0.1.0b14 before 0.1.0b15
vyperlang vyperfrom 0.4.1 through 0.5.0b1

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having a Moderate impact because successful exploitation requires an attacker to supply maliciously formatted source files that must be processed by the compiler. Vyper is not packaged or distributed within Red Hat Enterprise Linux or core Red Hat product offerings, which limits direct exposure on default installations. In user environments where standalone Vyper tooling is executed, risk is confined to compile-time processing rather than runtime network daemon compromise.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-114114.

Attack patterns (CAPEC)

  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON