Advisory record · GHSA-2r3x-4mrv-mcxf

Vyper: Memory corruption using function calls within tuples / nested calls

CVSS 8.3 HighEPSS 0.0028 · 21st percentile

Published by the GitHub Advisory Database at 6 Oct 2026, 15:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
vyperPyPI<0.2.60.2.6
Identifiers
GHSA-2r3x-4mrv-mcxf · CVE-2020-37286
Weakness (CWE)
CWE-129 · CWE-787
Published
6 Oct 2026
Updated
24 Oct 2026

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.

Written 1 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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

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.