Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vyper versions before 0.3.8 can allocate too few storage slots for contracts that declare very large arrays, because a floating-point rounding step in the slot calculation produces wrong results at large sizes. This can cause one storage variable to be overwritten by another, and the source describes the attack needing contract code that uses such arrays rather than an external action. Upgrade the vyper package to version 0.3.8 or later. The source gives no workaround.
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.0069, the 53rd percentile, on 5 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-6m97-7527-mh74
- OSV: GHSA-6m97-7527-mh74
- github.com/vyperlang/vyper/security/advisories/GHSA-6m97-7527-mh74
- nvd.nist.gov/vuln/detail/CVE-2023-46247
- github.com/vyperlang/vyper/commit/0bb7203b584e771b23536ba065a6efda457161bb
- github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-307.yaml
- github.com/vyperlang/vyper
- github.com/vyperlang/vyper/blob/6020b8bbf66b062d299d87bc7e4eddc4c9d1c157/vyper/semantics/validation/data_positions.py#L197