Advisory record · GHSA-w9g2-3w7p-72g9

Incorrect success value returned in vyper

CVSS 7.5 HighEPSS 0.0088 · 59th percentile

Published by the GitHub Advisory Database at 24 Apr 2023, 22:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
vyperPyPI>=0.3.1, <0.3.80.3.8
Identifiers
GHSA-w9g2-3w7p-72g9 · CVE-2023-30629 · PYSEC-2023-131
Weakness (CWE)
CWE-670
Published
24 Apr 2023
Updated
10 Sept 2026

Machine-written summary

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

Vyper versions from 0.3.1 before 0.3.8 are affected: when a contract calls raw_call with both max_outsize=0 and revert_on_failure=False, the compiler generates incorrect bytecode, so the returned success flag can be either True or False depending on memory contents. An attacker does not need access; any contract using this call pattern receives the wrong result, which can affect its logic. Upgrade to Vyper 0.3.8. As a workaround, set max_outsize to a value greater than 0.

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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0088, the 59th percentile, on 7 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.