CVE-2026-40072

web3.py affected by SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling

Published Apr 9, 2026 CVSS 4.0 · 1.7 Low EPSS < 1% KEV · Not listed
Description
web3.py allows you to interact with the Ethereum blockchain using Python. From 6.0.0b3 to before 7.15.0 and 8.0.0b2, web3.py implements CCIP Read / OffchainLookup (EIP-3668) by performing HTTP requests to URLs supplied by smart contracts in offchain_lookup_payload["urls"]. The implementation uses these contract-supplied URLs directly (after {sender} / {data} template substitution) without any destination validation. CCIP Read is enabled by default (global_ccip_read_enabled = True on all providers), meaning any application using web3.py's .call() method is exposed without explicit opt-in. This results in Server-Side Request Forgery (SSRF) when web3.py is used in backend services, indexers, APIs, or any environment that performs eth_call / .call() against untrusted or user-supplied contract addresses. A malicious contract can force the web3.py process to issue HTTP requests to arbitrary destinations, including internal network services and cloud metadata endpoints. This vulnerability is fixed in 7.15.0 and 8.0.0b2.

Analysis

AI-generated

Technical impact

The vulnerability stems from web3.py’s handling of the CCIP Read/OffchainLookup mechanism as defined by EIP‑3668. The library performs HTTP requests to URLs supplied by a smart contract without validating the destination, allowing an attacker to supply arbitrary URLs. This missing validation results in a Server‑Side Request Forgery that can be leveraged from any backend process that uses the library’s .call() method. The flaw can expose internal network resources or cloud metadata services to attackers through the library.

Affected Systems

The affected library is Ethereum’s web3.py. Versions starting with 6.0.0b3 up to but excluding 7.15.0 and including 8.0.0b2 are vulnerable. All providers have CCIP Read enabled by default, so any application that uses .call() with untrusted or user‑supplied contract addresses is at risk.

Risk and Exploitability

The CVSS score of 1.7 indicates a low‑severity flaw, and no EPSS information is available; the vulnerability is not listed in the CISA KEV catalog. The likely attack path involves a malicious smart contract returning an offchain_lookup_payload containing crafted URLs, causing a backend service running web3.py to issue requests to arbitrary endpoints. Because the library performs the calls automatically, no additional user interaction is required other than the execution of .call() against the contract. The lack of destination validation makes exploitation straightforward for an attacker who can control the contract data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade web3.py to version 7.15.0 or 8.0.0b2 to apply the vendor fix.
  • If upgrading is not immediately possible, disable global CCIP Read by setting global_ccip_read_enabled=False or configuring the provider to forbid offchain lookup.
  • Avoid calling .call() on contracts whose source is not trusted or that could return an offchain_lookup_payload.
  • Monitor outbound HTTP traffic from backend services for unexpected or suspicious requests to internal or cloud metadata endpoints.

Generated by OpenCVE AI on April 9, 2026 at 19:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-5hr4-253g-cpx2 web3.py: SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling
History
Type Values Removed Values Added
First Time appeared Apeworx
Apeworx web3.py
CPEs cpe:2.3:a:apeworx:web3.py:*:*:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:-:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta10:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta11:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta3:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta4:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta5:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta6:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta7:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta8:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:6.0.0:beta9:*:*:*:python:*:*
cpe:2.3:a:apeworx:web3.py:8.0.0:beta1:*:*:*:python:*:*
Vendors & Products Apeworx
Apeworx web3.py
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Type Values Removed Values Added
First Time appeared Ethereum
Ethereum web3.py
Vendors & Products Ethereum
Ethereum web3.py
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description web3.py allows you to interact with the Ethereum blockchain using Python. From 6.0.0b3 to before 7.15.0 and 8.0.0b2, web3.py implements CCIP Read / OffchainLookup (EIP-3668) by performing HTTP requests to URLs supplied by smart contracts in offchain_lookup_payload["urls"]. The implementation uses these contract-supplied URLs directly (after {sender} / {data} template substitution) without any destination validation. CCIP Read is enabled by default (global_ccip_read_enabled = True on all providers), meaning any application using web3.py's .call() method is exposed without explicit opt-in. This results in Server-Side Request Forgery (SSRF) when web3.py is used in backend services, indexers, APIs, or any environment that performs eth_call / .call() against untrusted or user-supplied contract addresses. A malicious contract can force the web3.py process to issue HTTP requests to arbitrary destinations, including internal network services and cloud metadata endpoints. This vulnerability is fixed in 7.15.0 and 8.0.0b2.
Title web3.py affected by SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling
Weaknesses CWE-918
References
Metrics cvssV4_0

{'score': 1.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 9, 2026, 7:37 PM
Reserved
Apr 9, 2026, 12:39 AM
Status
Analyzed
Published
Apr 9, 2026, 6:17 PM
Modified
Oct 26, 2026, 10:10 PM