<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T23:45:29.840894+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-45149</id>
    <title>CVE-2026-45149 — brace-expansion: Large numeric range defeats documented `max` DoS protection</title>
    <updated>2026-10-05T23:45:29.870995+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> juliangruber brace-expansion</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-45149"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jxxr-4gwj-5jf2</id>
    <title>GHSA-jxxr-4gwj-5jf2 — brace-expansion: Large numeric range defeats documented `max` DoS protection</title>
    <updated>2026-10-05T23:45:29.871059+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: brace-expansion</p>
<p>The `max` option was being applied too late:</p>
<p>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.</p>
<p>### Workaround</p>
<p>Ensure the string to be expanded doesn't contain more values than the desired `max` item count.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jxxr-4gwj-5jf2"/>
  </entry>
</feed>
