CVE Intelligence
High File handling

CVE-2026-114663 — Vyper 0.4.0b1 through 0.5.0b1 Name Shadowing of Imported Constants and Default Arguments

Vyper 0.4.0b1 through 0.5.0b1 miscompiles unfoldable constants and omitted default arguments from imported modules, because parse_Name resolves their names in the using function's scope rather than at declaration. When a contract's parameter, local, or loop variable shares such a name, attacker-influenced input can replace the intended value, including out-of-range values for narrow types such as uint8, corrupting validation or accounting logic.

Published Oct 21, 2026 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.18%
ahead of 7% of scored CVEs · Oct 26, 2026
Affects
Vyperlang
Vyper
CVSS base
8.4
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Vyperlang Vyper).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Vyperlang Vyper ≥ 0.4.0b1 and ≤ 0.5.0b1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.6 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
8.6 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
8.4 CVSS 3.1 High 2.5 5.9 disclosure@vulncheck.com via NIST National Vulnerability Database
8.4 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.4 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-706 · Use of Incorrectly-Resolved Name or Reference

Other CVEs with this weakness →

EPSS over time FIRST

Oct 22, 2026 → Oct 26, 2026 · 5 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Monitor file creation in web directories and paths with traversal sequences (../).
endpoint telemetry (EDR)file integrity (FIM)

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Deferred
    Oct 22, 2026 · NIST National Vulnerability Database
  • Affected products added · vyperlang/vyper
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • CVSS changed · 8.4
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • CVE published
    Oct 21, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 23, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

4 on the record

Elsewhere on this site

Vyperlang
every CVE for this vendor
File handling
same class
CWE-706
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114117 Vyper 0.3.8 through 0.5.0b1 Optimizer Miscompilation of msg.value | K in Ternary Branches 7d
  • CVE-2026-114118 Vyper 0.3.4 through 0.5.0b1 create_from_blueprint Offset Validation Bypass via Unsigned Wraparound 7d
  • CVE-2026-114114 Vyper through 0.5.0b1 Literal Value Substitution via Multi-byte Characters 7d
  • CVE-2026-114115 Vyper 0.3.8 through 0.5.0b1 Memory Misread via Ternary Nested Array Selection 7d
  • CVE-2026-114116 Vyper through 0.5.0b1 Literal Value Manipulation via Line Separators 7d
  • CVE-2021-48019 Vyper before 0.2.9 Incorrect RETURNDATASIZE in create_forwarder_to Proxies 7d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-114663 is "Vyper 0.4.0b1 through 0.5.0b1 Name Shadowing of Imported Constants and Default Arguments", rated High. It affects Vyper (Vyperlang); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.