Advisory record · GHSA-9x7f-gwxq-6f2c

Vyper's bounds check on built-in `slice()` function can be overflowed

CVSS 9.8 CriticalCriticalEPSS 0.0090 · 60th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 1 Feb 2024, 20:51 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-9x7f-gwxq-6f2c · CVE-2024-24561 · PYSEC-2024-149
Weakness (CWE)
CWE-119
Published
1 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 are affected. When the start or length argument to the built-in slice() function is not a literal, the runtime bounds check can overflow, letting an attacker read out-of-bounds storage, memory or calldata and corrupt the length of the resulting array. The attacker needs to supply the start or length value, which depends on the contract's design. Upgrade Vyper to 0.4.0 or later. The source gives few details on a workaround.

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.0090, the 60th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:36 UTC First seen by agentprime
  2. 31 Oct 2026, 14:36 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.