CVE-2025-26622
Vyperlang Vyper ≤ 0.4.1
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-26622 is a low-severity Incorrect Calculation (CWE-682) vulnerability in Vyperlang Vyper. Its CVSS base score is 2.3 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-26622 affects Vyper, a Pythonic smart contract language for the Ethereum Virtual Machine (EVM). The vulnerability resides in the `sqrt()` builtin function, which employs the Babylonian method to compute square roots of decimals. Due to improper handling of oscillating final states, the function may incorrectly return rounded-up results, potentially leading to precise calculation errors in compiled smart contracts.
Attackers with network access can exploit this vulnerability remotely with low complexity, requiring no privileges, no user interaction, and without changing the scope of impact. The CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) reflects high integrity impact, enabling manipulation of square root computations in affected smart contracts deployed on EVM-compatible blockchains. This could result in financial discrepancies or flawed logic in decentralized applications relying on accurate decimal square root calculations.
The Vyper security advisory and associated pull request indicate that the issue is being addressed, with a fix expected in version 0.4.1. Users are advised to upgrade to the patched release as soon as it becomes available, as no workarounds are known. Relevant resources include the GitHub security advisory at GHSA-2p94-8669-xg86 and pull request #4486.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4284
Vulnerability Data
vyper is a Pythonic Smart Contract Language for the EVM. Vyper `sqrt()` builtin uses the babylonian method to calculate square roots of decimals. Unfortunately, improper handling of the oscillating final states may lead to sqrt incorrectly returning rounded up results.…
more
This issue is being addressed and a fix is expected in version 0.4.1. Users are advised to upgrade as soon as the patched release is available. There are no known workarounds for this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation directly exercises calculations and can discover incorrect or unintended results used in security decisions.
Requiring documented development processes and standards can enforce coding rules and tool usage that reduce introduction of calculation errors.
Engineering principles applied during design and implementation can require verified algorithms and safe arithmetic that structurally avoid incorrect calculation results.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent incorrect calculations via reviews, testing, and verification in security-critical code.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect calculation flaws before deployment.
Secure development lifecycle mandates verification steps that catch incorrect calculations before they reach production.
Application security requirements can explicitly call for numeric accuracy and bounds checking.
Secure architecture principles include input validation and safe arithmetic design that reduce calculation errors.
Secure coding standards directly prohibit unsafe arithmetic and require defensive checks against incorrect results.