cve.bz

CVE-2026-114116 vyperlang vyper: Interpretation Conflict

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.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.

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-436 Interpretation Conflict
OWASP Top 10
A06:2025 Insecure Design
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-114116 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114116?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114116?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-114116 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.0b17
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 Moderate impact for Red Hat because successful exploitation requires an adversary to introduce specifically crafted source code and have a user or automated pipeline compile it. While the integrity consequences could be significant if altered constants are deployed in compiled artifacts, execution requires local user interaction and code contribution privileges rather than remote unauthenticated access. Furthermore, Vyper is not distributed with Red Hat Enterprise Linux, limiting the direct impact on Red Hat products.

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-114116.

Attack patterns (CAPEC)

  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling 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