CVE-2020-37286
Vyper 0.1.0b4 before 0.3.0 Memory Corruption via Nested Internal Function Calls
- High 8.3
Description
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.
Key facts
- Published
- 21 Oct 2026
- Last changed
- 27 Oct 2026
- Assigned by
- VulnCheck
- EPSS
- 0.284% likely to be exploited in the next 30 days, higher than 21.19% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.3CVSS 4.0, Highfrom the CNA (VulnCheck)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N - 6.5CVSS 3.1, Mediumfrom the CNA (VulnCheck)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| vyperlang | vyper |
|
Timeline
- 21 Oct 2026 Published