# Vyper has incorrectly allocated named re-entrancy locks

Advisory record · `GHSA-5824-cm3x-3c38`

- **Identifiers:** `GHSA-5824-cm3x-3c38` · `CVE-2023-39363` · `PYSEC-2023-142`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 9 Aug 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Aug 2023, 14:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `vyper` (PyPI): affected `>=0.2.15, <0.3.1`; fixed in `0.3.1`

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

Written 5 Nov 2026.

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

- 9.1 Critical, CVSS 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`, from 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](https://osv.dev/vulnerability/GHSA-5824-cm3x-3c38)

## Sources

- [GitHub Advisory Database: GHSA-5824-cm3x-3c38](https://github.com/advisories/GHSA-5824-cm3x-3c38)
- [OSV: GHSA-5824-cm3x-3c38](https://osv.dev/vulnerability/GHSA-5824-cm3x-3c38)
- <https://github.com/vyperlang/vyper/security/advisories/GHSA-5824-cm3x-3c38>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-39363>
- <https://github.com/vyperlang/vyper/pull/2439>
- <https://github.com/vyperlang/vyper/pull/2514>
- <https://github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-142.yaml>
- <https://github.com/vyperlang/vyper>
- <https://hackmd.io/@LlamaRisk/BJzSKHNjn>
- <https://hackmd.io/@vyperlang/HJUgNMhs2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5824-cm3x-3c38>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5824-cm3x-3c38/>. Everything for agents: <https://agentprime.io/llms.txt>.
