<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T09:50:46.641758+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/ghsa-27v5-c462-wpq7</id>
    <title>GHSA-27v5-c462-wpq7 — path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards</title>
    <updated>2026-10-05T09:50:46.661065+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: path-to-regexp</p>
<p>### Impact</p>
<p>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.</p>
<p>**Unsafe examples:**</p>
<p>```
/*foo-*bar-:baz
/*a-:b-*c-:d
/x/*a-:b/*c/y
```</p>
<p>**Safe examples:**</p>
<p>```
/*foo-:bar
/*foo-:bar-*baz
```</p>
<p>### Patches</p>
<p>Upgrade to version `8.4.0`.</p>
<p>### Workarounds</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-27v5-c462-wpq7"/>
  </entry>
</feed>
