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.

Attack Vector Network

Attack Complexity Low

Privileges Required None

Attack Requirements Present

User Interaction None

Vulnerable System Confidentiality Impact None

Vulnerable System Integrity Impact High

Vulnerable System Availability Impact Low

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact None

Integrity Impact High

Availability Impact Low

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
vyperlang vyper unaffected
Version Status Constraints
0.1.0b4 affected < 0.3.0
0.3.0 unaffected —

No data.

No data.

No data.

Project Subscriptions

Vendors Products
Vyperlang Subscribe
Vyper Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://github.com/vyperlang/vyper/security/advisories/GHSA-22wc-c9wj-6q2v cve-icon cve-icon
https://www.vulncheck.com/advisories/vyper-before-0.3.0-memory-corruption-via-internal-function-calls-in-arrays cve-icon cve-icon
History

Wed, 21 Oct 2026 00:45:00 +0000

Type Values Removed Values Added
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 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.
Title Vyper before 0.3.0 Memory Corruption via Internal Function Calls in Arrays
First Time appeared Vyperlang
Vyperlang vyper
Weaknesses CWE-787
CPEs cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:*:*:*
Vendors & Products Vyperlang
Vyperlang vyper
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L'}

cvssV4_0

{'score': 8.3, 'vector': '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'}

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-21T00:36:19.625Z

Reserved: 2026-10-20T21:52:06.584Z

Link: CVE-2021-48020

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-21T01:17:19.300

Modified: 2026-10-21T01:17:19.300

Link: CVE-2021-48020

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses