<?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, 05 Oct 2026 19:12:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45149 — brace-expansion: Large numeric range defeats documented `max` DoS protection</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-45149</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; juliangruber brace-expansion&lt;/p&gt;
&lt;p&gt;The brace-expansion library generates arbitrary strings containing a common prefix and suffix. From 5.0.0 to before 5.0.6, the max option was being applied too late. When expanding a single large numeric range like {1..10000000}, the sequence generation loop generates all 10 million intermediate elements before the max limit is applied With max=10, the output is correctly limited to 10 items, but the process still allocates ~505 MB and spends ~800ms building the full intermediate array. This vulnerability is fixed in 5.0.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; juliangruber brace-expansion&lt;/p&gt;
&lt;p&gt;The brace-expansion library generates arbitrary strings containing a common prefix and suffix. From 5.0.0 to before 5.0.6, the max option was being applied too late. When expanding a single large numeric range like {1..10000000}, the sequence generation loop generates all 10 million intermediate elements before the max limit is applied With max=10, the output is correctly limited to 10 items, but the process still allocates ~505 MB and spends ~800ms building the full intermediate array. This vulnerability is fixed in 5.0.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-45149</guid>
    </item>
    <item>
      <title>GHSA-jxxr-4gwj-5jf2 — brace-expansion: Large numeric range defeats documented `max` DoS protection</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jxxr-4gwj-5jf2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: brace-expansion&lt;/p&gt;
&lt;p&gt;The `max` option was being applied too late:&lt;/p&gt;
&lt;p&gt;When expanding a single large numeric range like `{1..10000000}`, the sequence generation loop generates all 10 million intermediate elements before the `max` limit is applied With `max=10`, the output is correctly limited to 10 items, but the process still allocates `~505 MB` and spends `~800ms` building the full intermediate array.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Ensure the string to be expanded doesn&amp;#39;t contain more values than the desired `max` item count.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: brace-expansion&lt;/p&gt;
&lt;p&gt;The `max` option was being applied too late:&lt;/p&gt;
&lt;p&gt;When expanding a single large numeric range like `{1..10000000}`, the sequence generation loop generates all 10 million intermediate elements before the `max` limit is applied With `max=10`, the output is correctly limited to 10 items, but the process still allocates `~505 MB` and spends `~800ms` building the full intermediate array.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Ensure the string to be expanded doesn&amp;#39;t contain more values than the desired `max` item count.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jxxr-4gwj-5jf2</guid>
    </item>
  </channel>
</rss>
