CVE-2025-50181: urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation
urllib3 handles redirects and retries using the same mechanism, which is controlled by the Retry object. The most common way to disable redirects is at the request level, as follows: However, it is also possible to disable redirects, for all requests, by instantiating a PoolManager and specifying retries in a way that disable redirects: However, the retries parameter is currently ignored, which means all the above…
Published Jun 18, 2025 · Updated Dec 22, 2025
Affected packages
urllib3
- Ecosystem
- PyPI
- Affected
- < 2.5.0
- Fixed in
- 2.5.0
- Check
pip show urllib3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
urllib3 handles redirects and retries using the same mechanism, which is controlled by the Retry object. The most common way to disable redirects is at the request level, as follows:
resp = urllib3.request("GET", "https://httpbin.org/redirect/1", redirect=False)
print(resp.status)
# 302However, it is also possible to disable redirects, for all requests, by instantiating a PoolManager and specifying retries in a way that disable redirects:
import urllib3
http = urllib3.PoolManager(retries=0) # should raise MaxRetryError on redirect
http = urllib3.PoolManager(retries=urllib3.Retry(redirect=0)) # equivalent to the above
http = urllib3.PoolManager(retries=False) # should return the first response
resp = http.request("GET", "https://httpbin.org/redirect/1")However, the retries parameter is currently ignored, which means all the above examples don't disable redirects.
Affected usages
Passing retries on PoolManager instantiation to disable redirects or restrict their number.
By default, requests and botocore users are not affected.
Impact
Redirects are often used to exploit SSRF vulnerabilities. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects at the PoolManager level will remain vulnerable.
Remediation
You can remediate this vulnerability with the following steps:
- Upgrade to a patched version of urllib3. If your organization would benefit from the continued support of urllib3 1.x, please contact [[email protected]](mailto:[email protected]) to discuss sponsorship or contribution opportunities.
- Disable redirects at the
request()level instead of thePoolManager()level.
Credited to sandumjacob, illia-v, pquentin, sethmlarson.
References
- https://github.com/urllib3/urllib3/security/advisories/GHSA-pq67-6m6q-mj2v
- https://github.com/urllib3/urllib3/commit/f05b1329126d5be6de501f9d1e3e36738bc08857
- https://nvd.nist.gov/vuln/detail/CVE-2025-50181
- https://github.com/urllib3/urllib3/releases/tag/2.5.0
- https://github.com/advisories/GHSA-pq67-6m6q-mj2v
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-97687
urllib3: HTTPS proxy TLS configuration may be ignored or overridden
high7.6Sep 30, 2026CVE-2026-97688
urllib3: Chunked Deflate streaming can enter an infinite loop
medium6.9Sep 30, 2026CVE-2026-97689
urllib3: HTTPResponse.stream()/read_chunked() buffers an unbounded chunk-size line into memory
high8.9Sep 30, 2026CVE-2026-44431
urllib3: Sensitive headers forwarded across origins in proxied low-level redirects
high5.3May 11, 2026CVE-2026-44432
urllib3: Decompression-bomb safeguards bypassed in parts of the streaming API
high7.5May 11, 2026CVE-2026-21441
Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)
high7.5Jan 7, 2026
