Advisory

GHSA-2r3x-4mrv-mcxf

Also known as: CVE-2020-37286

Summary

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

Details

Impact
When performing a function call inside a tuple or as an argument inside another function call, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.

Example code:

@internal
def _foo(a: uint256, b: uint256, c: uint256) -> (uint256, uint256, uint256, uint256, uint256):
    return 1, a, b, c, 5

@internal
def _foo2() -> uint256:
    a: uint256[10] = [6,7,8,9,10,11,12,13,15,16]
    return 4

@external
def foo() -> (uint256, uint256, uint256, uint256, uint256):
    return self._foo(2, 3, self._foo2())

Please see #2186 for further information

Patches
This problem was fixed in #2186, and released as a part of `v0.2.6`.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-10-06 15:22 UTC
Modified
2026-10-24 02:56 UTC

Affected packages and fixes

vyper

PyPI · All systems

Affected

  • introduced 0, fixed 0.2.6 (ecosystem)

Fixed versions

0.2.6

Fix

  • Fixed version 0.2.6
    pip install --upgrade vyper==0.2.6

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences