Answer in brief
CVE-2026-114116 records a Medium severity (CVSS 6.0) vulnerability in Vyper through 0.5.0b1 Literal Value Manipulation via Line Separators. The current sources do not mark it as known exploited. The current feed maps vyperlang/vyper (generic), vyperlang/vyper (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps vyperlang/vyper (generic), vyperlang/vyper (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vyperlang/vypergeneric | >=0.1.0b1 <0.1.0b17 | 0.1.0b17 |
| vyperlang/vypergeneric | >=0.4.1 <=0.5.0b1 | Not reported |
Published upstream
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.