CVE-2024-32481

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.8% (54th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. Starting in version 0.3.8 and prior to version 0.4.0b1, when looping over a range of the form range(start, start + N), if start is negative, the execution will always revert. This issue is caused by an incorrect assertion inserted by the code generation of the range stmt.parse_For_range(). The issue arises when start is signed, instead of using sle, le is used and start is interpreted as an unsigned integer for the comparison. If it is a negative number, its 255th bit is set to 1 and is hence interpreted as a very large unsigned integer making the assertion always fail. Any contract having a range(start, start + N) where start is a signed integer with the possibility for start to be negative is affected. If a call goes through the loop while supplying a negative start the execution will revert. Version 0.4.0b1 fixes the issue.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 25, 2024

Last Modified

May 5, 2025

References (8)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
vyper0.3.10 ... 0.3.9 (8 versions)
  • 0.3.8 up to 0.4.0: fixed in 0.4.0
  • 0.3.8 up to 0.4.0b1: fixed in 0.4.0b1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 191 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:07 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 15:15 UTCEPSS rescore
  5. 2026-10-05 17:41 UTCEPSS rescore
  6. 2026-10-04 23:20 UTCEPSS rescore
  7. 2026-10-03 14:24 UTCEPSS rescore
  8. 2026-10-01 19:48 UTCEPSS rescore
  9. 2026-09-30 19:43 UTCEG score recompute
  10. 2026-09-30 15:01 UTCEPSS rescore
  11. 2026-09-29 15:17 UTCEPSS rescore
  12. 2026-09-28 13:49 UTCEPSS rescore
  13. 2026-09-27 13:43 UTCEPSS rescore
  14. 2026-09-26 15:57 UTCEPSS rescore
  15. 2026-09-26 00:23 UTCEPSS rescore
  16. 2026-09-24 14:01 UTCEPSS rescore
  17. 2026-09-23 13:46 UTCEPSS rescore
  18. 2026-09-23 13:46 UTCEPSS rescore
  19. 2026-09-22 14:46 UTCEPSS rescore
  20. 2026-09-21 23:45 UTCOSV refresh
  21. 2026-09-20 20:14 UTCEPSS rescore
  22. 2026-09-19 15:40 UTCEPSS rescore
  23. 2026-09-18 19:26 UTCEPSS rescore
  24. 2026-09-16 14:06 UTCEPSS rescore
  25. 2026-09-16 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:08 UTCEPSS rescore
  2. 2026-09-15 03:08 UTCEPSS rescore
  3. 2026-09-13 16:45 UTCEPSS rescore
  4. 2026-09-12 14:59 UTCEPSS rescore
  5. 2026-09-11 14:51 UTCEPSS rescore
  6. 2026-09-11 09:35 UTCEPSS rescore
  7. 2026-09-08 21:58 UTCEPSS rescore
  8. 2026-09-07 15:59 UTCEPSS rescore
  9. 2026-09-06 13:46 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-05 15:26 UTCEPSS rescore
  12. 2026-09-04 13:58 UTCEPSS rescore
  13. 2026-09-04 05:05 UTCEPSS rescore
  14. 2026-09-02 19:08 UTCOSV refresh
  15. 2026-09-02 14:10 UTCEPSS rescore
  16. 2026-09-01 13:52 UTCEPSS rescore
  17. 2026-08-30 19:15 UTCEPSS rescore
  18. 2026-08-30 01:20 UTCEPSS rescore
  19. 2026-08-28 21:39 UTCEPSS rescore
  20. 2026-08-27 14:23 UTCEPSS rescore
  21. 2026-08-26 14:44 UTCEPSS rescore
  22. 2026-08-25 13:47 UTCEPSS rescore
  23. 2026-08-24 14:15 UTCEPSS rescore
  24. 2026-08-23 00:17 UTCEPSS rescore
  25. 2026-08-21 23:47 UTCEPSS rescore
  26. 2026-08-20 22:53 UTCEPSS rescore
  27. 2026-08-19 17:02 UTCEPSS rescore
  28. 2026-08-19 17:02 UTCEPSS rescore
  29. 2026-08-18 13:46 UTCEPSS rescore
  30. 2026-08-18 13:46 UTCEPSS rescore
  31. 2026-08-17 13:45 UTCEPSS rescore
  32. 2026-08-16 14:54 UTCEPSS rescore
  33. 2026-08-16 11:38 UTCOSV refresh
  34. 2026-08-16 02:13 UTCEPSS rescore
  35. 2026-08-15 01:28 UTCEPSS rescore
  36. 2026-08-13 21:59 UTCEPSS rescore
  37. 2026-08-12 13:49 UTCEPSS rescore
  38. 2026-08-11 13:40 UTCEPSS rescore
  39. 2026-08-10 23:58 UTCEPSS rescore
  40. 2026-08-09 13:45 UTCEPSS rescore
  41. 2026-08-08 16:35 UTCEPSS rescore
  42. 2026-08-07 16:25 UTCEPSS rescore
  43. 2026-08-06 13:45 UTCEPSS rescore
  44. 2026-08-05 19:16 UTCEPSS rescore
  45. 2026-08-04 15:08 UTCEPSS rescore
  46. 2026-08-04 10:36 UTCEPSS rescore
  47. 2026-08-03 10:34 UTCEPSS rescore
  48. 2026-08-02 02:25 UTCEPSS rescore
  49. 2026-08-02 02:25 UTCEPSS rescore
  50. 2026-08-01 06:06 UTCOSV refresh
  51. 2026-08-01 04:14 UTCEPSS rescore
  52. 2026-07-30 16:26 UTCEPSS rescore
  53. 2026-07-30 16:26 UTCEPSS rescore
  54. 2026-07-30 01:29 UTCEPSS rescore
  55. 2026-07-28 15:34 UTCEPSS rescore
  56. 2026-07-27 14:11 UTCEPSS rescore
  57. 2026-07-26 14:53 UTCEPSS rescore
  58. 2026-07-26 14:53 UTCEPSS rescore
  59. 2026-07-25 14:16 UTCEPSS rescore
  60. 2026-07-24 14:16 UTCEPSS rescore
  61. 2026-07-23 14:17 UTCEPSS rescore
  62. 2026-07-23 02:36 UTCEG score recompute
  63. 2026-07-22 14:07 UTCEPSS rescore
  64. 2026-07-21 15:23 UTCEPSS rescore
  65. 2026-07-20 17:06 UTCEPSS rescore
  66. 2026-07-19 14:30 UTCEPSS rescore
  67. 2026-07-19 14:30 UTCEPSS rescore
  68. 2026-07-19 02:28 UTCEPSS rescore
  69. 2026-07-19 02:28 UTCEPSS rescore
  70. 2026-07-18 10:03 UTCEPSS rescore
  71. 2026-07-18 10:03 UTCEPSS rescore
  72. 2026-07-16 17:01 UTCEPSS rescore
  73. 2026-07-15 16:56 UTCEPSS rescore
  74. 2026-07-15 16:56 UTCEPSS rescore
  75. 2026-07-15 01:59 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-32481?
CVE-2024-32481 is a medium vulnerability published on April 25, 2024. Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. Starting in version 0.3.8 and prior to version 0.4.0b1, when looping over a range of the form range(start, start + N), if start is negative, the execution will always revert. This issue is caused by an incorrect assertion…
When was CVE-2024-32481 disclosed?
CVE-2024-32481 was first published on April 25, 2024, with the most recent update on May 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-32481 actively exploited?
CVE-2024-32481 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32481?
CVE-2024-32481 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2024-32481?
A fix for CVE-2024-32481 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32481

Explore →

Is Your Infrastructure Affected by CVE-2024-32481?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs