Vyper through 0.5.0b1 Literal Value Manipulation via Line Separators
Impact
Vyper versions 0.1.0b1 before 0.1.0b17 and 0.4.1 through 0.5.0b1 have a weakness where an attacker contributing source code can manipulate numeric literals. This is due to the parser treating certain characters as line breaks. The impact is unclear.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
vyperlang · VulnCheck
vyper
2 ranges
vyperlang · VulnCheck
vyper
Package identity
pkg:pypi/vyperExplore vyper →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0.1.0b1 → before 0.1.0b17
python versions
unaffected
0.1.0b17
python versions
Other versions: unaffected
vyperlang · VulnCheck
vyper
1 range
vyperlang · VulnCheck
vyper
Package identity
pkg:pypi/vyperExplore vyper →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0.4.1 → through 0.5.0b1
python versions
Other versions: unaffected
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-114116View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
VulnCheck · platform conditions
Any condition may hold
Vulnerable product
cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*From (inclusive): 0.1.0b1
Before: 0.1.0b17
Any condition may hold
Vulnerable product
cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*From (inclusive): 0.4.1
Through (inclusive): 0.5.0b1
Original applicability statements
[
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.1.0b1",
"versionEndExcluding": "0.1.0b17"
}
]
}
]
},
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.4.1",
"versionEndIncluding": "0.5.0b1"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.