CVE-2023-30629Network attack vector

Incorrect call success result via erroneous MLOAD

Published Apr 24, 2023 · Updated Feb 12, 2025

Incorrect control flow in Vyper 0.3.1 through 0.3.7 allows remote attackers to influence contracts through raw_call results. The raw_call builder emits CALL followed by MLOAD when revert_on_failure is false and max_outsize is zero, reading memory instead of the stack-held success flag. An affected contract must use that option combination, after which control flow can follow an incorrect True or False result determined by memory contents.

CVSS severity7.5
High
EPSS probability0.88%
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 control flow in Vyper 0.3.1 through 0.3.7 allows remote attackers to influence contracts through raw_call results. The raw_call builder emits CALL followed by MLOAD when revert_on_failure is false and max_outsize is zero, reading memory instead of the stack-held success flag. An affected contract must use that option combination, after which control flow can follow an incorrect True or False result determined by memory contents.

The record

CVE
CVE-2023-30629
Published
Apr 24, 2023
Updated
Feb 12, 2025
Vendor
Vyper
Product
Vyper
Classifications
CWE-670
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 24, 2023CVE publishedPublication date reported by the CVE source.
  2. Feb 12, 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.1, <= 0.3.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Vyper · Vyperversion=>= 0.3.1, <= 0.3.7

Published CVSS scores

8.7GitHub Advisory DatabaseCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
7.5GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 exploitUnconfirmed

Weakness, pattern, technique

CWE-670Always-Incorrect Control Flow Implementation

Public exploit references

No public exploit references are available in this record.

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