# CVE-2026-42175: requests-hardened: Server-Side Request Forgery (SSRF) in requests-hardened RFC 6598

> Attackers can bypass SSRF protections to access internal services in the RFC 6598 address space, impacting environments using this CIDR range.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-vh75-fwv3-pqrh, PYSEC-2026-3050

## What is CVE-2026-42175?

CVE-2026-42175 is a medium-severity server-side request forgery vulnerability in saleor requests-hardened, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

requests-hardened is a library that overrides the default behaviors of the requests library, and adds new security features. Prior to , the SSRF protection in requests-hardened fails to block IP addresses within the RFC 6598 Shared Address Space (100.64.0.0/10). An attacker who can supply arbitrary URLs to requests-hardened could exploit this gap to access internal services hosted within 100.64.0.0/10. This is for example relevant in environments such as AWS EKS where 100.64.0.0/10 is commonly used as the default pod CIDR. The impact is environment-dependent, deployments that utilize the affected CIDR range for internal networking are exposed to SSRF bypass, while others may not be affected. This vulnerability is fixed in .

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

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

3 open source packages ship an affected version, including requests-hardened.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `requests-hardened` | PyPI | All versions | 1.2.1 |
| `requests-hardened` | PyPI | All versions | 1.2.1 |
| `requests-hardened` | PyPI | All versions | 1.2.1 |

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

Upgrade requests-hardened to 1.2.1 or later.

## Is CVE-2026-42175 being exploited?

There is no known exploitation of CVE-2026-42175 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42175 is a medium-severity server-side request forgery vulnerability in saleor requests-hardened, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42175 in the wild and no public exploit code.

Affected packages and fixed versions:
- requests-hardened (PyPI): affected all versions; fixed in 1.2.1
- requests-hardened (PyPI): affected all versions; fixed in 1.2.1
- requests-hardened (PyPI): affected all versions; fixed in 1.2.1

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-42175/ (Markdown: https://insights.sbomify.com/CVE-2026-42175/index.md)
```

## Sources

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

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