<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 14:17:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-50181 — urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-50181</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; urllib3&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; urllib3&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-50181</guid>
    </item>
    <item>
      <title>GHSA-pq67-6m6q-mj2v — urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pq67-6m6q-mj2v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: urllib3&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;```python
resp = urllib3.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;, redirect=False)
print(resp.status)
# 302
```&lt;/p&gt;
&lt;p&gt;However, it is also possible to disable redirects, for all requests, by instantiating a `PoolManager` and specifying `retries` in a way that disable redirects:&lt;/p&gt;
&lt;p&gt;```python
import urllib3&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;resp = http.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;However, the `retries` parameter is currently ignored, which means all the above examples don&amp;#39;t disable redirects.&lt;/p&gt;
&lt;p&gt;## Affected usages&lt;/p&gt;
&lt;p&gt;Passing `retries` on `PoolManager` instantiation to disable redirects or restrict their number.&lt;/p&gt;
&lt;p&gt;By default, requests and botocore users are not affected.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;You can remediate this vulnerability with the following steps:&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched version of urllib3. If your organization would benefit from the continued supp…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: urllib3&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;```python
resp = urllib3.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;, redirect=False)
print(resp.status)
# 302
```&lt;/p&gt;
&lt;p&gt;However, it is also possible to disable redirects, for all requests, by instantiating a `PoolManager` and specifying `retries` in a way that disable redirects:&lt;/p&gt;
&lt;p&gt;```python
import urllib3&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;resp = http.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;However, the `retries` parameter is currently ignored, which means all the above examples don&amp;#39;t disable redirects.&lt;/p&gt;
&lt;p&gt;## Affected usages&lt;/p&gt;
&lt;p&gt;Passing `retries` on `PoolManager` instantiation to disable redirects or restrict their number.&lt;/p&gt;
&lt;p&gt;By default, requests and botocore users are not affected.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;You can remediate this vulnerability with the following steps:&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched version of urllib3. If your organization would benefit from the continued supp…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pq67-6m6q-mj2v</guid>
    </item>
    <item>
      <title>PYSEC-2026-1999 — urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-1999</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: urllib3&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;```python
resp = urllib3.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;, redirect=False)
print(resp.status)
# 302
```&lt;/p&gt;
&lt;p&gt;However, it is also possible to disable redirects, for all requests, by instantiating a `PoolManager` and specifying `retries` in a way that disable redirects:&lt;/p&gt;
&lt;p&gt;```python
import urllib3&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;resp = http.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;However, the `retries` parameter is currently ignored, which means all the above examples don&amp;#39;t disable redirects.&lt;/p&gt;
&lt;p&gt;## Affected usages&lt;/p&gt;
&lt;p&gt;Passing `retries` on `PoolManager` instantiation to disable redirects or restrict their number.&lt;/p&gt;
&lt;p&gt;By default, requests and botocore users are not affected.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;You can remediate this vulnerability with the following steps:&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched version of urllib3. If your organization would benefit from the continued supp…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: urllib3&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;```python
resp = urllib3.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;, redirect=False)
print(resp.status)
# 302
```&lt;/p&gt;
&lt;p&gt;However, it is also possible to disable redirects, for all requests, by instantiating a `PoolManager` and specifying `retries` in a way that disable redirects:&lt;/p&gt;
&lt;p&gt;```python
import urllib3&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;resp = http.request(&amp;#34;GET&amp;#34;, &amp;#34;https://httpbin.org/redirect/1&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;However, the `retries` parameter is currently ignored, which means all the above examples don&amp;#39;t disable redirects.&lt;/p&gt;
&lt;p&gt;## Affected usages&lt;/p&gt;
&lt;p&gt;Passing `retries` on `PoolManager` instantiation to disable redirects or restrict their number.&lt;/p&gt;
&lt;p&gt;By default, requests and botocore users are not affected.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;You can remediate this vulnerability with the following steps:&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched version of urllib3. If your organization would benefit from the continued supp…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-1999</guid>
    </item>
  </channel>
</rss>
