Skip to content
Fencer Intel
medium 4.3

CVE-2021-41122 json

Bounds check missing for decimal args in Vyper

published 5y ago modified 4mo ago also GHSA-c7pr-343r-5c46 , PYSEC-2021-366 , EUVD-2021-0460

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Vyper is a Pythonic Smart Contract Language for the EVM. In affected versions external functions did not properly validate the bounds of decimal arguments. The can lead to logic errors. This issue has been resolved in version 0.3.0.

Patch / fix

  • pypi vyper 0.3.0
  • vyperlang vyper 0.3.0

Is CVE-2021-41122 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/vyperlang/vyper/security/advisories/GHSA-c7pr-343r-5c46 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi vyper
<0.3.0
0.3.0

Affected products

  • vyperlang vyper

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.