Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vyper versions 0.2.15 through before 0.3.1 (0.2.15, 0.2.16 and 0.3.0) allocate named re-entrancy locks incorrectly, giving each function that uses a named lock its own lock regardless of key. An attacker who can reach a contract compiled with these versions can exploit cross-function re-entrancy when a function with a shared key makes an external call before updating storage. Upgrade to Vyper 0.3.1 or higher.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.1 | Critical | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:A | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0082, the 58th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:36 UTC First seen by agentprime
- 31 Oct 2026, 14:36 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5824-cm3x-3c38
- OSV: GHSA-5824-cm3x-3c38
- github.com/vyperlang/vyper/security/advisories/GHSA-5824-cm3x-3c38
- nvd.nist.gov/vuln/detail/CVE-2023-39363
- github.com/vyperlang/vyper/pull/2439
- github.com/vyperlang/vyper/pull/2514
- github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-142.yaml
- github.com/vyperlang/vyper
- hackmd.io/@LlamaRisk/BJzSKHNjn
- hackmd.io/@vyperlang/HJUgNMhs2