<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T15:39:05.735133+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-66418</id>
    <title>CVE-2025-66418 — urllib3 allows an unbounded number of links in the decompression chain</title>
    <updated>2026-09-29T15:39:05.741711+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> urllib3</p>
<p>urllib3 is a user-friendly HTTP client library for Python. Starting in version 1.24 and prior to 2.6.0, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data. This vulnerability is fixed in 2.6.0.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-66418"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-gm62-xv2j-4w53</id>
    <title>GHSA-gm62-xv2j-4w53 — urllib3 allows an unbounded number of links in the decompression chain</title>
    <updated>2026-09-29T15:39:05.741829+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: urllib3</p>
<p>## Impact</p>
<p>urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., `Content-Encoding: gzip, zstd`).</p>
<p>However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.</p>
<p>## Affected usages</p>
<p>Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.</p>
<p>## Remediation</p>
<p>Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.</p>
<p>If upgrading is not immediately possible, use [`preload_content=False`](https://urllib3.readthedocs.io/en/2.5.0/advanced-usage.html#streaming-and-i-o) and ensure that `resp.headers["content-encoding"]` contains a safe number of encodings before reading the response content.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-gm62-xv2j-4w53"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-1998</id>
    <title>PYSEC-2026-1998 — urllib3 allows an unbounded number of links in the decompression chain</title>
    <updated>2026-09-29T15:39:05.741901+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: urllib3</p>
<p>## Impact</p>
<p>urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., `Content-Encoding: gzip, zstd`).</p>
<p>However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.</p>
<p>## Affected usages</p>
<p>Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.</p>
<p>## Remediation</p>
<p>Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.</p>
<p>If upgrading is not immediately possible, use [`preload_content=False`](https://urllib3.readthedocs.io/en/2.5.0/advanced-usage.html#streaming-and-i-o) and ensure that `resp.headers["content-encoding"]` contains a safe number of encodings before reading the response content.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-1998"/>
  </entry>
</feed>
