Storage corruption due to variables overwritten by re-entrancy locks
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Background When attempting to use the v0.2.14 release, @pandadefi discovered an issue using the `@nonreentrant` decorator. ### Impact Reentrancy protection storage slots get allocated to the same slots as storage variables, leading to the corruption of storage variables when using the `@nonreentrant` decorator. ### Patches This issue was fixed in v0.2.15 in #2391, #2379 ### Workarounds Don't use the `@nonreentrant` decorator in these versions.
Why it matters now
Fix Fixed vyper (PyPI): 0.2.15
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | vyper (PyPI) | 0.2.13 to before 0.2.15 | 0.2.15 | Patch available | GHSA-7f92-rr6w-cq64 |
- vyper (PyPI) Vendor— Affected 0.2.13 to before 0.2.15 Fixed in 0.2.15 Patch available GHSA-7f92-rr6w-cq64
Remediation
- Fix · GHSA-7f92-rr6w-cq64 vyper (PyPI) Fixed in 0.2.15 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-7f92-rr6w-cq64
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences