Advisory record · GHSA-52xq-j7v9-v4v2

Vyper negative array index bounds checks

CVSS 9.8 CriticalCriticalEPSS 0.015 · 75th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 7 Feb 2024, 17:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
vyperPyPI<0.4.00.4.0
Identifiers
GHSA-52xq-j7v9-v4v2 · CVE-2024-24563 · PYSEC-2024-150
Weakness (CWE)
CWE-129
Published
7 Feb 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Vyper versions before 0.4.0 (PyPI package vyper, referred to here as the Vyper compiler) allow signed integers to index arrays that are declared for unsigned indexes, and the runtime bounds check can be passed by very large negative values when the array is at least 2**255 elements long. An attacker who can supply the index value to a contract can cause unexpected array access, which may bypass developer assumptions about bounds. The source says a search found no production contracts affected. Upgrade to vyper 0.4.0 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.015, the 75th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:35 UTC First seen by agentprime
  2. 31 Oct 2026, 14:35 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.