Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The Python package vyper, versions before 0.2.6, has a memory corruption bug that occurs when a function call is placed inside a tuple or used as an argument to another function call, because of an incorrect pointer to the top of the stack. The source does not describe what an attacker must do to trigger it or what the impact would be beyond memory corruption. Upgrade vyper to version 0.2.6 or later.
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 |
|---|---|---|---|---|
| 8.3 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0028, the 21st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2r3x-4mrv-mcxf
- OSV: GHSA-2r3x-4mrv-mcxf
- github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf
- github.com/vyperlang/vyper/pull/2186
- github.com/vyperlang/vyper/commit/74ba67d4bec5f8be4f05759e37d2bfb1463e0441
- github.com/vyperlang/vyper
- github.com/vyperlang/vyper/releases/tag/v0.2.6