cve.bz

CVE-2020-37287 vyperlang vyper: Incorrect Calculation of Buffer Size

8.2 highEPSS 0.3%Fix available

High (8.2) in vyperlang vyper. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in vyper 0.2.6.

On this page
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.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-131 Incorrect Calculation of Buffer Size
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • vyper (PyPI): fixed in 0.2.6

Ask an AI about this CVE

Show the promptExplain CVE-2020-37287 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-37287?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-37287?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-37287 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
vyperlang vyperbefore 0.2.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4v7v-gqf9-ww2gPyPIvyper<0.2.60.2.6

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate by Red Hat because exploitation depends on smart contracts implementing specific signatures with nested or multidimensional data parameters, limiting the scope of contracts vulnerable to stack misalignment. In typical Red Hat enterprise environments, Vyper is not provided as part of standard platform packages or runtimes, significantly minimizing default attack surfaces. Consequently, potential integrity loss is restricted to specialized custom deployments that compile and interact with contracts structured with affected composite arguments.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-37287.

Attack patterns (CAPEC)

  • CAPEC-47 Buffer Overflow via Parameter Expansion Likelihood: Medium · Severity: High
  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON