Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vyper versions before 0.3.8 are vulnerable to a storage allocator overflow, because the storage allocator does not guard against allocation overflows. An attacker who can call a contract compiled with an affected version may be able to overwrite storage variables such as an owner variable. Upgrade to Vyper 0.3.8 or later. The source gives few details, and no workaround is listed.
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 |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0070, the 53rd percentile, on 19 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-mgv8-gggw-mrg6
- OSV: GHSA-mgv8-gggw-mrg6
- github.com/vyperlang/vyper/security/advisories/GHSA-mgv8-gggw-mrg6
- nvd.nist.gov/vuln/detail/CVE-2023-30837
- github.com/vyperlang/vyper/commit/0bb7203b584e771b23536ba065a6efda457161bb
- github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-76.yaml
- github.com/vyperlang/vyper