cve.bz

CVE-2026-111171 ethereum web3.py: SSRF

6.3 mediumEPSS 0.3%Fix available

Medium (6.3) in ethereum web3.py. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in web3 7.15.0, 8.0.0b2.

On this page
Web3.py 7.15.0 through 7.16.0 and 8.0.0b2 through 8.0.0 contains a server-side request forgery vulnerability because _check_ip_blocked() does not unwrap IPv4-mapped IPv6 addresses in CCIP Read URL validation. Malicious contracts can return OffchainLookup URLs with IPv4-mapped IPv6 hosts or AAAA records, making clients with CCIP Read enabled send requests to loopback, private, or link-local services.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • web3 (PyPI): fixed in 7.15.0, 8.0.0b2

Ask an AI about this CVE

Show the promptExplain CVE-2026-111171 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111171?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111171?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111171 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ethereum web3.pyfrom 7.15.0 through 7.16.0
ethereum web3.pyfrom 8.0.0b2 through 8.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5hr4-253g-cpx2PyPIweb3>=6.0.0b3 <7.15.07.15.0
GHSA-5hr4-253g-cpx2PyPIweb3>=8.0.0b1 <8.0.0b28.0.0b2
PYSEC-2026-3414PyPIweb3>=6.0.0b3 <7.15.0
>=8.0.0b1 <8.0.0b2
7.15.0, 8.0.0b2

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON