<?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>Mon, 28 Sep 2026 17:07:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53539 — Python-Multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53539</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Kludex python-multipart&lt;/p&gt;
&lt;p&gt;Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, when parsing application/x-www-form-urlencoded bodies, QuerystringParser located the field separator with a two step lookup: it first scanned the entire remaining buffer for &amp;amp;, and only when no &amp;amp; existed anywhere ahead did it fall back to scanning for ;. For a body that uses ; as the separator and contains no &amp;amp;, every field iteration performed a full failed &amp;amp; scan over the entire remaining buffer before locating the nearby ;. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk. An attacker can submit a small crafted body of the form a;a;a;... and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes. This vulnerability is fixed in 0.0.30.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Kludex python-multipart&lt;/p&gt;
&lt;p&gt;Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, when parsing application/x-www-form-urlencoded bodies, QuerystringParser located the field separator with a two step lookup: it first scanned the entire remaining buffer for &amp;amp;, and only when no &amp;amp; existed anywhere ahead did it fall back to scanning for ;. For a body that uses ; as the separator and contains no &amp;amp;, every field iteration performed a full failed &amp;amp; scan over the entire remaining buffer before locating the nearby ;. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk. An attacker can submit a small crafted body of the form a;a;a;... and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes. This vulnerability is fixed in 0.0.30.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53539</guid>
    </item>
    <item>
      <title>GHSA-5rvq-cxj2-64vf — python-multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5rvq-cxj2-64vf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: python-multipart&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When parsing `application/x-www-form-urlencoded` bodies, `QuerystringParser` located the field separator with a two step lookup: it first scanned the entire remaining buffer for `&amp;amp;`, and only when no `&amp;amp;` existed anywhere ahead did it fall back to scanning for `;`. For a body that uses `;` as the separator and contains no `&amp;amp;`, every field iteration performed a full failed `&amp;amp;` scan over the entire remaining buffer before locating the nearby `;`. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk.&lt;/p&gt;
&lt;p&gt;An attacker can submit a small crafted body of the form `a;a;a;...` and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `python_multipart/multipart.py`, both the `FIELD_NAME` and `FIELD_DATA` states located the next separator like this:&lt;/p&gt;
&lt;p&gt;```python
sep_pos = data.find(b&amp;#34;&amp;amp;&amp;#34;, i)
if sep_pos == -1:
    sep_pos = data.find(b&amp;#34;;&amp;#34;, i)
```&lt;/p&gt;
&lt;p&gt;`data.find(b&amp;#34;&amp;amp;&amp;#34;, i)` scans from `i` to the end of the buffer and returns `-1` only when there is no `&amp;amp;` anywhere in the remainder. For a `;` separated body with no `&amp;amp;`, this failed full buffer scan repeats once per field, making parsing quadratic in the body length.&lt;/p&gt;
&lt;p&gt;For example, a 1 MiB url encoded body consisting of `a;` repeated ~500,000 times, submitted with `Content-Type: application/x-www-form-urlencoded`, causes the parser to perform on the order of 10^11 byte comparisons, consuming several seconds of C…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: python-multipart&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When parsing `application/x-www-form-urlencoded` bodies, `QuerystringParser` located the field separator with a two step lookup: it first scanned the entire remaining buffer for `&amp;amp;`, and only when no `&amp;amp;` existed anywhere ahead did it fall back to scanning for `;`. For a body that uses `;` as the separator and contains no `&amp;amp;`, every field iteration performed a full failed `&amp;amp;` scan over the entire remaining buffer before locating the nearby `;`. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk.&lt;/p&gt;
&lt;p&gt;An attacker can submit a small crafted body of the form `a;a;a;...` and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `python_multipart/multipart.py`, both the `FIELD_NAME` and `FIELD_DATA` states located the next separator like this:&lt;/p&gt;
&lt;p&gt;```python
sep_pos = data.find(b&amp;#34;&amp;amp;&amp;#34;, i)
if sep_pos == -1:
    sep_pos = data.find(b&amp;#34;;&amp;#34;, i)
```&lt;/p&gt;
&lt;p&gt;`data.find(b&amp;#34;&amp;amp;&amp;#34;, i)` scans from `i` to the end of the buffer and returns `-1` only when there is no `&amp;amp;` anywhere in the remainder. For a `;` separated body with no `&amp;amp;`, this failed full buffer scan repeats once per field, making parsing quadratic in the body length.&lt;/p&gt;
&lt;p&gt;For example, a 1 MiB url encoded body consisting of `a;` repeated ~500,000 times, submitted with `Content-Type: application/x-www-form-urlencoded`, causes the parser to perform on the order of 10^11 byte comparisons, consuming several seconds of C…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5rvq-cxj2-64vf</guid>
    </item>
    <item>
      <title>PYSEC-2026-3036 — python-multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-3036</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: python-multipart&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When parsing `application/x-www-form-urlencoded` bodies, `QuerystringParser` located the field separator with a two step lookup: it first scanned the entire remaining buffer for `&amp;amp;`, and only when no `&amp;amp;` existed anywhere ahead did it fall back to scanning for `;`. For a body that uses `;` as the separator and contains no `&amp;amp;`, every field iteration performed a full failed `&amp;amp;` scan over the entire remaining buffer before locating the nearby `;`. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk.&lt;/p&gt;
&lt;p&gt;An attacker can submit a small crafted body of the form `a;a;a;...` and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `python_multipart/multipart.py`, both the `FIELD_NAME` and `FIELD_DATA` states located the next separator like this:&lt;/p&gt;
&lt;p&gt;```python
sep_pos = data.find(b&amp;#34;&amp;amp;&amp;#34;, i)
if sep_pos == -1:
    sep_pos = data.find(b&amp;#34;;&amp;#34;, i)
```&lt;/p&gt;
&lt;p&gt;`data.find(b&amp;#34;&amp;amp;&amp;#34;, i)` scans from `i` to the end of the buffer and returns `-1` only when there is no `&amp;amp;` anywhere in the remainder. For a `;` separated body with no `&amp;amp;`, this failed full buffer scan repeats once per field, making parsing quadratic in the body length.&lt;/p&gt;
&lt;p&gt;For example, a 1 MiB url encoded body consisting of `a;` repeated ~500,000 times, submitted with `Content-Type: application/x-www-form-urlencoded`, causes the parser to perform on the order of 10^11 byte comparisons, consuming several seconds of C…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: python-multipart&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When parsing `application/x-www-form-urlencoded` bodies, `QuerystringParser` located the field separator with a two step lookup: it first scanned the entire remaining buffer for `&amp;amp;`, and only when no `&amp;amp;` existed anywhere ahead did it fall back to scanning for `;`. For a body that uses `;` as the separator and contains no `&amp;amp;`, every field iteration performed a full failed `&amp;amp;` scan over the entire remaining buffer before locating the nearby `;`. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk.&lt;/p&gt;
&lt;p&gt;An attacker can submit a small crafted body of the form `a;a;a;...` and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `python_multipart/multipart.py`, both the `FIELD_NAME` and `FIELD_DATA` states located the next separator like this:&lt;/p&gt;
&lt;p&gt;```python
sep_pos = data.find(b&amp;#34;&amp;amp;&amp;#34;, i)
if sep_pos == -1:
    sep_pos = data.find(b&amp;#34;;&amp;#34;, i)
```&lt;/p&gt;
&lt;p&gt;`data.find(b&amp;#34;&amp;amp;&amp;#34;, i)` scans from `i` to the end of the buffer and returns `-1` only when there is no `&amp;amp;` anywhere in the remainder. For a `;` separated body with no `&amp;amp;`, this failed full buffer scan repeats once per field, making parsing quadratic in the body length.&lt;/p&gt;
&lt;p&gt;For example, a 1 MiB url encoded body consisting of `a;` repeated ~500,000 times, submitted with `Content-Type: application/x-www-form-urlencoded`, causes the parser to perform on the order of 10^11 byte comparisons, consuming several seconds of C…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-3036</guid>
    </item>
  </channel>
</rss>
