CVE-2022-24845Network attack vector

Incorrect behavior via unchecked external returns

Published Apr 13, 2022 · Updated Apr 22, 2025

Integer overflow in Vyper before 0.3.2 allows remote attackers to cause incorrect smart-contract behavior via crafted external calls. The compiler fails to clamp returndata from interface calls such as returns_int128() when those calls occur inside complex expressions, allowing out-of-range values to be interpreted as valid types. Exploitation requires a contract that makes the affected external call and a callee capable of returning out-of-bounds data; the resulting impact is incorrect contract behavior with confidentiality, integrity, and availability consequences described by the published CVSS assessments.

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

Integer overflow in Vyper before 0.3.2 allows remote attackers to cause incorrect smart-contract behavior via crafted external calls. The compiler fails to clamp returndata from interface calls such as returns_int128() when those calls occur inside complex expressions, allowing out-of-range values to be interpreted as valid types. Exploitation requires a contract that makes the affected external call and a callee capable of returning out-of-bounds data; the resulting impact is incorrect contract behavior with confidentiality, integrity, and availability consequences described by the published CVSS assessments.

The record

CVE
CVE-2022-24845
Published
Apr 13, 2022
Updated
Apr 22, 2025
Vendor
Vyper
Product
Vyper
Classifications
CWE-190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 13, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 22, 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.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Vyper · Vyperversion=< 0.3.2

Published CVSS scores

8.8GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
9.8NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.5NVDAV:N/AC:L/Au:N/C:P/I:P/A:P

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 exploitUnconfirmed

Weakness, pattern, technique

CWE-190Integer Overflow or Wraparound

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