<?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, 05 Oct 2026 09:50:47 +0000</lastBuildDate>
    <item>
      <title>GHSA-27v5-c462-wpq7 — path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-27v5-c462-wpq7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: path-to-regexp&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path.&lt;/p&gt;
&lt;p&gt;**Unsafe examples:**&lt;/p&gt;
&lt;p&gt;```
/*foo-*bar-:baz
/*a-:b-*c-:d
/x/*a-:b/*c/y
```&lt;/p&gt;
&lt;p&gt;**Safe examples:**&lt;/p&gt;
&lt;p&gt;```
/*foo-:bar
/*foo-:bar-*baz
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Upgrade to version `8.4.0`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If developers are using multiple wildcard parameters, they can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: path-to-regexp&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path.&lt;/p&gt;
&lt;p&gt;**Unsafe examples:**&lt;/p&gt;
&lt;p&gt;```
/*foo-*bar-:baz
/*a-:b-*c-:d
/x/*a-:b/*c/y
```&lt;/p&gt;
&lt;p&gt;**Safe examples:**&lt;/p&gt;
&lt;p&gt;```
/*foo-:bar
/*foo-:bar-*baz
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Upgrade to version `8.4.0`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If developers are using multiple wildcard parameters, they can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-27v5-c462-wpq7</guid>
    </item>
  </channel>
</rss>
