CVE-2020-37287

Vyper before 0.2.6 Call Stack Corruption via Complex Type Function Arguments

MEDIUM
5.9
CVSS Score
Published: October 21, 2026 at 12:36 AM UTC
Updated: October 28, 2026 at 03:17 PM UTC
1 product affected across 1 vendorVyper

Using vyper by vyperlang?

Get instant alerts when new vulnerabilities affect vyper - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Vyper before 0.2.6 contains a call stack corruption vulnerability that causes incorrect function outputs when complex types with non-base members are passed as arguments. Contracts passing multi-dimensional arrays or structs to internal or external functions receive corrupted values because the compiler assumed each subtype size is 32.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions
Vendor states this is fixed in 0.2.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMVulnCheck
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-131

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card