CVE-2024-24563Public exploitNetwork attack vector

Contract bounds bypass via negative array indexes

Published Feb 7, 2024 · Updated Jun 17, 2025

Improper array-index validation in Vyper before 0.4.0 allows remote attackers to bypass contract array bounds via signed indexes. The type checker accepts int256 indexes for unsigned arrays, and code generation interprets negative values in two's complement, so sufficiently large arrays pass the runtime upper-bound check. Exploitation requires a contract compiled with an affected release, an attacker-controlled signed index, and an extremely large array; the result can expose invariant-protected elements or trigger unexpected contract behavior.

CVSS severity9.8
Critical
EPSS probability1.54%
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

Improper array-index validation in Vyper before 0.4.0 allows remote attackers to bypass contract array bounds via signed indexes. The type checker accepts int256 indexes for unsigned arrays, and code generation interprets negative values in two's complement, so sufficiently large arrays pass the runtime upper-bound check. Exploitation requires a contract compiled with an affected release, an attacker-controlled signed index, and an extremely large array; the result can expose invariant-protected elements or trigger unexpected contract behavior.

The record

CVE
CVE-2024-24563
Published
Feb 7, 2024
Updated
Jun 17, 2025
Vendor
Vyper
Product
Vyper
Classifications
CWE-129
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 7, 2024CVE publishedPublication date reported by the CVE source.
  2. Jun 17, 2025Record 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.10

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Vyper · Vyperversion=<= 0.3.10

Published CVSS scores

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

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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-129Improper Validation of Array Index

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