← Back
CVE-2026-44431
medium
CVSS 5.3
Information Disclosure in urllib3 (CVE-2026-44431)
Summary
vulnerability in urllib3 (CVE-2026-44431). Risk of unauthorized operations or information disclosure. Exploitable via ``Authorization``. Mitigation: upgrade to `2.7.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44431** has been found in urllib3.
Attackers can target a specific entry point like ``Authorization`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade urllib3 to **2.7.0** or later.
If unsure, ask your IT team or search "urllib3 CVE-2026-44431" on the vendor's site.
CVE-2026-44431 (urllib3) — CWE-200 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Authorization` / `Cookie` / `Retry.DEFAULT_REMOVE_HEADERS_ON_REDIRECT` / `HTTPConnection`
Patched: `2.7.0` — apply immediately
Workaround: avoid using this low-level redirect flow for cross-origin redirects.
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
**information disclosure** (CWE-200) exists in urllib3. Attackers reach the vulnerable code path via ``Authorization`` without authentication.
📍 Affected scope
urllib3 — . Attack surface: `Authorization` / `Cookie` / `Retry.DEFAULT_REMOVE_HEADERS_ON_REDIRECT` / `HTTPConnection`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.7.0**.
🛡️ Workaround
Workaround: avoid using this low-level redirect flow for cross-origin redirects.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'urllib3' .` 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 'urllib3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `urllib3` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
avoid using this low-level redirect flow for cross-origin redirects.パッチが適用されるまでの応急処置として、avoid using this low-level redirect flow for cross-origin redirects. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade urllib3 to 2.7.0ステージング環境で 2.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
urllib3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.0"}]}]
PyPI
urllib3
[{"type":"ECOSYSTEM","events":[{"introduced":"1.23"},{"fixed":"2.7.0"}]}]