cve.bz

CVE-2021-48020 vyperlang vyper: Out-of-bounds Write

8.3 highEPSS 0.3%Fix available

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

On this page
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 are performed inside arrays. Contracts placing internal calls in nested array elements, external call arguments, struct literals, or raw_log topics can have memory corrupted, producing incorrect contract behavior.

Severity

CVSS 4.0

8.3 high
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

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 21st 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-787 Out-of-bounds Write
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.12

Ask an AI about this CVE

Show the promptExplain CVE-2021-48020 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-48020?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-48020?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-2021-48020 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 vyperfrom 0.1.0b4 before 0.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-22wc-c9wj-6q2vPyPIvyper<0.2.120.2.12

References

Check your stackJSON