# CVE-2026-111171: Web3.py 7.15.0 through 7.16.0 and 8.0.0b2 through 8.0.0 CCIP-Read SSRF Bypass

> Attackers can bypass IP restrictions in Web3.py CCIP Read to access internal services via IPv4-mapped IPv6 addresses.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-w8h5-xcmp-474f

## What is CVE-2026-111171?

CVE-2026-111171 is a medium-severity server-side request forgery vulnerability in ethereum web3.py, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-111171?


## How do I fix CVE-2026-111171?

Upgrade to a fixed version.

## Is CVE-2026-111171 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111171 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111171 and fix it if it is affected.

What it is: CVE-2026-111171 is a medium-severity server-side request forgery vulnerability in ethereum web3.py, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111171 exists.

Affected product: ethereum web3.py. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111171/ (Markdown: https://insights.sbomify.com/CVE-2026-111171/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111171
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111171
- OSV: https://osv.dev/vulnerability/CVE-2026-111171

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111171/
Summaries are generated and may contain mistakes; the official description above is the record.