requests-hardened is Vulnerable to Server-Side Request Forgery

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0031, the 23rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 15:01 UTC First seen by agentprime
2. 31 Oct 2026, 15:01 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-vh75-fwv3-pqrh
• OSV: GHSA-vh75-fwv3-pqrh
• github.com/saleor/requests-hardened/security/advisories/GHSA-vh75-fwv3-pqrh
• nvd.nist.gov/vuln/detail/CVE-2026-42175
• github.com/saleor/requests-hardened/commit/a266b3958bb142bca515b3c230fdea19fbda327c
• github.com/saleor/requests-hardened/commit/b7403f88d3b3689e57435b75b51691a160aaeef5
• github.com/saleor/requests-hardened
• github.com/saleor/requests-hardened/releases/tag/v1.2.1

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.