Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2020-37287high8.2

Vyper before 0.2.6 Call Stack Corruption via Complex Type Function Arguments

Impact

Vyper before 0.2.6 has a call stack corruption vulnerability when passing complex types as function arguments, causing incorrect outputs. This affects contracts using multi-dimensional arrays or structs. The weakness is due to an incorrect calculation of buffer size.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

vyperlang · VulnCheck

vyper

2 ranges
VulnCheck version evidence

Package identity

pkg:pypi/vyperExplore vyper →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 0.2.6

python versions

unaffected

0.2.6

python versions

unknown

Other versions: unaffected

Original source 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.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2020-37287

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-131 ↗

Incorrect Calculation of Buffer Size

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*

Before: 0.2.6

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "0.2.6"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-21
CISA-ADP

Additional data publisher

2026-10-28

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources
github.com/vyperlang/vyper/security/advisories/GHSA-4v7v-gqf9-ww2g
vendor-advisoryVulnCheck
www.vulncheck.com/advisories/vyper-before-0.2.6-call-stack-corruption-via-complex-type-function-arguments
third-party-advisoryVulnCheck