<?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://cve.radiocsirt.org</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, 16 Nov 2026 21:47:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-126190 — Soup Sieve: Polynomial-time denial of service in the descendant combinator</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-126190</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; facelessuser soupsieve&lt;/p&gt;
&lt;p&gt;Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 4.0, Soup Sieve repeatedly walks the same ancestors while matching descendant combinators, and each additional descendant combinator raises the polynomial degree of the work on deeply nested attacker-influenced HTML or XML. Applications using selectors such as section div div through select(), select_one(), or Beautiful Soup CSS APIs against untrusted documents can have a worker occupied for seconds or minutes, while trusted-only document processing is not affected. Selectors compiled with NOCACHE continue to use the old uncached behavior. This issue is fixed in version 4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; facelessuser soupsieve&lt;/p&gt;
&lt;p&gt;Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 4.0, Soup Sieve repeatedly walks the same ancestors while matching descendant combinators, and each additional descendant combinator raises the polynomial degree of the work on deeply nested attacker-influenced HTML or XML. Applications using selectors such as section div div through select(), select_one(), or Beautiful Soup CSS APIs against untrusted documents can have a worker occupied for seconds or minutes, while trusted-only document processing is not affected. Selectors compiled with NOCACHE continue to use the old uncached behavior. This issue is fixed in version 4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-126190</guid>
    </item>
    <item>
      <title>GHSA-mmhr-3c5m-f64f — Soup Sieve: Polynomial-time denial of service in the descendant combinator</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mmhr-3c5m-f64f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: soupsieve&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Matching a selector that uses the descendant combinator (`a b`) takes time that grows polynomially with how deeply the document is nested, and each extra descendant combinator in the selector raises the degree by one. A selector with `k` descendant combinators takes `O(n^(k+1))` time on a chain of `n` nested elements.&lt;/p&gt;
&lt;p&gt;An attacker who controls the HTML or XML that an application passes to Soup Sieve (directly, or through Beautiful Soup&amp;#39;s `select()`, `select_one()`, `css.select()`, etc.) can send a very small, deeply nested document that keeps a CPU busy for seconds to minutes against an ordinary selector such as `section div div`.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;To match `a b`, Soup Sieve checks each element against `b` and then walks up through its ancestors looking for one that matches `a`. When the selector has more descendant combinators, the rest of the selector is tried again from each ancestor on that walk, and so on for every combinator. Nothing was reused between walks, so the same ancestors were matched against the same part of the selector over and over.&lt;/p&gt;
&lt;p&gt;The worst case is when the leftmost part of the selector never matches, as in `section div div` against a document of nested `&amp;lt;div&amp;gt;` with no `&amp;lt;section&amp;gt;`: every walk goes all the way to the root and no search can stop early.&lt;/p&gt;
&lt;p&gt;### Timings&lt;/p&gt;
&lt;p&gt;Example timings with `html.parser` on Soup Sieve 3.0.4 and 4.0, using a document of nested `&amp;lt;div&amp;gt;` (5 bytes each) and no matches:&lt;/p&gt;
&lt;p&gt;| Nesting depth | Input size | Selector | 3.0.4 | 4.0…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: soupsieve&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Matching a selector that uses the descendant combinator (`a b`) takes time that grows polynomially with how deeply the document is nested, and each extra descendant combinator in the selector raises the degree by one. A selector with `k` descendant combinators takes `O(n^(k+1))` time on a chain of `n` nested elements.&lt;/p&gt;
&lt;p&gt;An attacker who controls the HTML or XML that an application passes to Soup Sieve (directly, or through Beautiful Soup&amp;#39;s `select()`, `select_one()`, `css.select()`, etc.) can send a very small, deeply nested document that keeps a CPU busy for seconds to minutes against an ordinary selector such as `section div div`.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;To match `a b`, Soup Sieve checks each element against `b` and then walks up through its ancestors looking for one that matches `a`. When the selector has more descendant combinators, the rest of the selector is tried again from each ancestor on that walk, and so on for every combinator. Nothing was reused between walks, so the same ancestors were matched against the same part of the selector over and over.&lt;/p&gt;
&lt;p&gt;The worst case is when the leftmost part of the selector never matches, as in `section div div` against a document of nested `&amp;lt;div&amp;gt;` with no `&amp;lt;section&amp;gt;`: every walk goes all the way to the root and no search can stop early.&lt;/p&gt;
&lt;p&gt;### Timings&lt;/p&gt;
&lt;p&gt;Example timings with `html.parser` on Soup Sieve 3.0.4 and 4.0, using a document of nested `&amp;lt;div&amp;gt;` (5 bytes each) and no matches:&lt;/p&gt;
&lt;p&gt;| Nesting depth | Input size | Selector | 3.0.4 | 4.0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mmhr-3c5m-f64f</guid>
    </item>
  </channel>
</rss>
