Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-40072: CWE-918: Server-Side Request Forgery (SSRF) in ethereum web3.py

0
Low
VulnerabilityCVE-2026-40072cvecve-2026-40072cwe-918
Published: Thu Apr 09 2026 (04/09/2026, 17:41:14 UTC)
Source: CVE Database V5
Vendor/Project: ethereum
Product: web3.py

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in ethereum's web3. py library versions from 6. 0. 0b3 up to but not including 7. 15. 0, and from 8. 0. 0b1 up to but not including 8. 0. 0b2.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/09/2026, 18:06:17 UTC

Technical Analysis

web3.py versions >=6.0.0b3 and <7.15.0, and >=8.0.0b1 and <8.0.0b2 implement CCIP Read / OffchainLookup (EIP-3668) by making HTTP requests to URLs specified by smart contracts in offchain_lookup_payload["urls"] without validating these URLs. Since CCIP Read is enabled by default, any backend service using web3.py's .call() method with untrusted contract addresses is vulnerable to SSRF. A malicious contract can cause the web3.py process to send HTTP requests to arbitrary destinations, including internal networks and cloud metadata endpoints. This vulnerability is resolved in versions 7.15.0 and 8.0.0b2.

Potential Impact

An attacker controlling a malicious smart contract can exploit this vulnerability to cause backend services using vulnerable versions of web3.py to make arbitrary HTTP requests. This can lead to unauthorized access to internal network resources or cloud metadata services. However, the overall impact is rated low based on the CVSS 4.0 score of 1.7, reflecting limited attack complexity and impact scope.

Mitigation Recommendations

Upgrade web3.py to version 7.15.0 or later, or 8.0.0b2 or later, where this SSRF vulnerability is fixed. Until upgraded, avoid using .call() with untrusted or user-supplied contract addresses. Patch status is not explicitly stated as 'patchAvailable' but the fix is included in the specified versions, so upgrading is the recommended remediation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-09T00:39:12.204Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69d7e6ff1cc7ad14dafe8de8

Added to database: 4/9/2026, 5:50:55 PM

Last enriched: 4/9/2026, 6:06:17 PM

Last updated: 4/9/2026, 7:08:29 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses