CVE-2024-32481Public exploitNetwork attack vector

Contract-call reversion via unsigned comparison of signed start

Published Apr 25, 2024 · Updated Aug 2, 2024

Incorrect code generation in Vyper 0.3.8 through 0.3.10 allows remote attackers to force affected smart-contract calls to revert. stmt.parse_For_range() emits an unsigned le assertion for a signed start value, so a negative value is interpreted as a very large integer and the assertion fails. The contract must contain range(start, start + N) with a signed start that a caller can make negative, preventing that invocation from completing.

CVSS severity5.3
Medium
EPSS probability0.80%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect code generation in Vyper 0.3.8 through 0.3.10 allows remote attackers to force affected smart-contract calls to revert. stmt.parse_For_range() emits an unsigned le assertion for a signed start value, so a negative value is interpreted as a very large integer and the assertion fails. The contract must contain range(start, start + N) with a signed start that a caller can make negative, preventing that invocation from completing.

The record

CVE
CVE-2024-32481
Published
Apr 25, 2024
Updated
Aug 2, 2024
Vendor
Vyper
Product
Vyper
Classifications
CWE-681
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 25, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 0.3.8, < 0.4.0b1
  2. Affected versionversion=0.3.8 <=0.4.0b1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Vyper · Vyperversion=>= 0.3.8, < 0.4.0b1; version=0.3.8 <=0.4.0b1

Published CVSS scores

5.3GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-681Incorrect Conversion between Numeric Types

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo