← Back
CVE-2026-42175
medium
CVSS 6.5
SSRF (Server-Side Request Forgery) in requests-hardened (CVE-2026-42175)
Summary
SSRF in requests-hardened (CVE-2026-42175). Confidential information can be exposed externally. Mitigation: upgrade to `1.2.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42175** has been found in requests-hardened.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade requests-hardened to **1.2.1** or later.
If unsure, ask your IT team or search "requests-hardened CVE-2026-42175" on the vendor's site.
CVE-2026-42175 (requests-hardened) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.2.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in requests-hardened.
📍 Affected scope
requests-hardened — .
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.2.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'requests-hardened' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'requests-hardened' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `requests-hardened` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade requests-hardened to 1.2.1ステージング環境で 1.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
requests-hardened
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.1"}]}]
References
- web https://github.com/saleor/requests-hardened/commit/a266b3958bb142bca515b3c230fdea19fbda327c
- web https://github.com/saleor/requests-hardened/commit/b7403f88d3b3689e57435b75b51691a160aaeef5
- web https://github.com/saleor/requests-hardened/releases/tag/v1.2.1
- web https://github.com/saleor/requests-hardened/security/advisories/GHSA-vh75-fwv3-pqrh
- web https://nvd.nist.gov/vuln/detail/CVE-2026-42175
- web https://github.com/advisories/GHSA-vh75-fwv3-pqrh