CVE-2025-50181 | urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation

Exp

urllib3 is a user-friendly HTTP client library for Python. Prior to 2.5.0, it is possible to disable redirects for all requests by instantiating a PoolManager and specifying retries in a way that disable redirects. By default, requests and botocore users are not affected. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects at the PoolManager level will remain vulnerable. This issue has been patched in version 2.5.0.

Published: 2025-06-19 Last update: 2025-12-22 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-50181 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.08%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-50181

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-50181

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-15 0.01% 0.08% +0.07%
2 2025-06-19 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-50181

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 3.6 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]

Weakness enumeration for CVE-2025-50181

GitHub Security Advisory for CVE-2025-50181

GHSA-pq67-6m6q-mj2v · Severity: medium · Ecosystem: pip — urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation

OS Trackers for CVE-2025-50181

vendor priority summary link
alpine — CVE-2025-50181: 1 source package rows (py3-urllib3); 27 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 27. https://security.alpinelinux.org/vuln/CVE-2025-50181
debian not yet assigned CVE-2025-50181 not yet assigned priority: Debian including 1 source packages (python-urllib3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-50181
redhat medium — https://access.redhat.com/security/cve/CVE-2025-50181
suse medium CVE-2025-50181 severity moderate: SUSE including 260 source package names (0.1.6-1.2:python311-urllib3-2.0.7-150400.7.21.1, 0.20250329.151219-6.4:python311-urllib3-2.0.7-150400.7.21.1, …), 673 product×package rows across 301 product lines (Container bci/kiwi, Container containers/lmcache-lmstack-router, … (301 product lines)): Fixed 445, Known Affected 228. https://www.suse.com/security/cve/CVE-2025-50181/
ubuntu medium CVE-2025-50181 medium priority: Ubuntu including 2 source packages (python-pip, python-urllib3), 18 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, trusty, upstream, xenial): released 12, not-affected 5, needs-triage 1. https://ubuntu.com/security/CVE-2025-50181

Affected software / configurations for CVE-2025-50181

Vendor Product Version Raw CPE
python urllib3 < 2.5.0 cpe:2.3:a:python:urllib3:*:*:*:*:*:*:*:*

References for CVE-2025-50181

cvelogic Threat Intelligence