CVE-2026-114663 vyperlang CVE debrief

Who should care

Vyper users and developers should assess exposure and prioritize remediation due to the potential for validation or accounting logic corruption. Operators, platforms, vulnerability-management teams, and security teams may be impacted and should review the official advisories for further details and verify the vulnerability's impact on their systems.

Why it matters

Vyper 0.4.0b1 through 0.5.0b1 vulnerability allows attacker-influenced input to corrupt validation or accounting logic, requiring assessment and remediation for Vyper users.

• Potential corruption of validation or accounting logic
• Possible exploitation through attacker-influenced input
• Need for verification of Vyper versions and usage
• Potential impact on systems using Vyper 0.4.0b1 through 0.5.0b1

Technical summary

Vyper 0.4.0b1 through 0.5.0b1 miscompiles unfoldable constants and omitted default arguments from imported modules, allowing attacker-influenced input to corrupt validation or accounting logic. This occurs when a contract's parameter, local, or loop variable shares a name with an imported constant or default argument, potentially leading to validation or accounting logic corruption. The vulnerability requires assessment and remediation for Vyper users and developers to prevent potential exploitation and corruption of validation or accounting logic.

Defensive priority

High-priority assessment and remediation recommended for Vyper users

Recommended defensive actions

• Assess exposure and prioritize remediation for Vyper 0.4.0b1 through 0.5.0b1
• Review and update Vyper versions to ensure usage of a fixed version
• Monitor for potential exploitation attempts
• Verify Vyper versions and usage in managed environments
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Official CVE Program record and NVD vulnerability detail page provide information on the vulnerability. Vendor advisory and third-party advisory provide additional context. The CVE record was published on 2026-10-22T01:43:46.942Z and has not been modified since then. Evidence is limited to publicly available information and may not be comprehensive. Defenders should verify the vulnerability's impact on their systems and review the official advisories for further details.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.