CVE-2021-41121: Memory corruption in vyper package

vyper Updated 02 Oct 2025

Summary

12/10/2021
Yes i
High
7.5

CVE-2021-41121: Memory corruption when returning a literal struct with a private call inside of it. Affects vyper versions < 0.3.0. Fixed in 0.3.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The vyper package is a Python package available on PyPI. It is used for writing smart contracts for the Ethereum blockchain. Vyper provides a higher-level language compared to Solidity, making it easier to write secure and efficient smart contracts. However, a vulnerability has been identified in the package that can lead to memory corruption.

Vulnerability Detail

The vulnerability in vyper occurs when a function call is performed inside a literal struct. Due to an incorrect pointer to the top of the stack, a memory corruption issue arises. This vulnerability has a high severity level with a CVSS score of 7.5. If exploited, it can lead to various consequences, including unauthorized access, data manipulation, and potential remote code execution.

How To Fix

Latest published version: 0.4.3 as of 22 Oct 2026

pip install --upgrade "vyper==0.4.3"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.3.0

This is the first release that contains the fix.

pip install --upgrade "vyper==0.3.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround available for this vulnerability. It is crucial to update the package to the fixed version as soon as possible.

Conclusion

In conclusion, the vyper package is vulnerable to a memory corruption issue that can have severe consequences if exploited. It is crucial for users to update their package to version 0.3.0 or higher to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for vyper →

Share this vulnerability

FAQ

The vyper package is used for writing smart contracts for the Ethereum blockchain. It provides a higher-level language compared to Solidity.

The vulnerability can lead to memory corruption, which may result in unauthorized access, data manipulation, and potential remote code execution.

To fix this vulnerability, update the vyper package to version 0.3.0 or higher using the command: pip install --upgrade vyper.

No, there is no specific workaround available for this vulnerability. Updating the package is the recommended solution.

The vulnerability has a high severity level with a CVSS score of 7.5.

Related vulnerabilities

Recent vulnerabilities recorded for vyper.

How To Fix

Latest published version: 0.4.3 as of 22 Oct 2026

pip install --upgrade "vyper==0.4.3"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.3.0

This is the first release that contains the fix.

pip install --upgrade "vyper==0.3.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback