Read the docs
TI-2020-20047 Aliases CVE-2020-37286

Memory corruption in Vyper via nested internal function calls

Priority LOW 36CWE-787Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · High · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Vyper from 0.1.0b4 before 0.3.0 uses an incorrect stack tip pointer when internal function calls appear inside tuples or nested calls, which causes an out-of-bounds write (CWE-787). Contracts that use such calls as tuple elements, call arguments or builtin arguments like concat or ecrecover can return corrupted values or pass wrong arguments to external calls. A network attacker with no privileges and no user interaction can trigger the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

Description from the CNA

Vyper from 0.1.0b4 before 0.3.0 contains a memory corruption vulnerability caused by an incorrect stack tip pointer when internal function calls appear inside tuples or nested calls. Contracts using such calls as tuple elements, call arguments, or builtin arguments like concat or ecrecover can return corrupted values or pass wrong arguments to external calls.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00284 21st percentileScored 2026-11-07
Fix Fixed vyper (vyperlang): 0.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
vyperlangvyper0.1.0b4 to before 0.3.00.3.0Patch availableCNA
  • vyper Vendorvyperlang Affected 0.1.0b4 to before 0.3.0 Fixed in 0.3.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*——vyperlang
  • cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:* Versions — — ·vyperlang

Remediation

Upgrade vyper to version 0.3.0, the fixed version.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

  • Fix · CNA vyper (vyperlang) Fixed in 0.3.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    vyperlang vyper 0.3.0

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2021-22763 Memory corruption in Vyper internal calls within arraysPriority LOW 36
    Show all 2 records →

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-21 Threatist record created from CVE-2020-37286
  2. 2026-10-22 Priority changed: MEDIUM → LOW
  3. 2026-10-27 CISA SSVC decision points changed
  4. 2026-11-02 Affected versions changed · Red Hat
  5. 2026-11-02 CVSS score added · Red Hat

References

Advisory 1

  • TI-2024-16182 Vyper bounds check on built-in `slice()` function can be overflowed CVSS 3.1CRITICAL 9.8
  • TI-2024-14992 concat built-in can corrupt memory in vyper CVSS 3.1CRITICAL 9.8
  • TI-2024-16184 Vyper array negative index vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2022-08657 Integer bounds error in Vyper CVSS 3.1CRITICAL 9.8
  • TI-2022-11796 Multiple evaluation of contract address in call in vyper CVSS 3.1HIGH 8.2
  • TI-2026-78730 Optimizer miscompilation of msg.value | K in Vyper ternary branches CVSS 4.0HIGH 8.2
See all 52 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences