How severe is GHSA-7f92-rr6w-cq64?

No CVSS score has been assigned to GHSA-7f92-rr6w-cq64 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7f92-rr6w-cq64?

GHSA-7f92-rr6w-cq64 affects the following packages: vyper (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-7f92-rr6w-cq64?

Update vyper to 0.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7f92-rr6w-cq64 is resolved across your whole dependency graph.

How do I detect GHSA-7f92-rr6w-cq64 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vyper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7f92-rr6w-cq64 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-7f92-rr6w-cq64 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7f92-rr6w-cq64 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-7f92-rr6w-cq64 published, and has it been updated?

GHSA-7f92-rr6w-cq64 was published on August 5, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Storage corruption due to variables overwritten by re-entrancy locksGHSA-7f92-rr6w-cq64

Fix: vyperlang/vyper#2379

GHSA-7f92-rr6w-cq64 is a security vulnerability in vyper. A fix is available for vyper — see the affected versions and patch details below.

Published

Aug 5, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍vyper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`vyper`	≥ 0.2.13&&< 0.2.15	0.2.15`pip install --upgrade 'vyper==0.2.15'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vyper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vyper to 0.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7f92-rr6w-cq64 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-7f92-rr6w-cq64 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works