CVE-2024-52798

Workarounds

Avoid using two parameters within a single path segment, when the separator is not . (e.g. no /:a-:b). Alternatively, you can define the regex used for both parameters and ensure they do not overlap to allow backtracking.

References

• https://github.com/advisories/GHSA-9wv6-86v2-598j
• https://blakeembrey.com/posts/2024-09-web-redos/

The regular expression that is vulnerable to backtracking can be generated in versions before 0.1.12 of path-to-regexp, originally reported in CVE-2024-45296

A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use. Typical impact: denial of service when input is crafted to trigger backtracking.

CVE-2024-52798 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.12); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade to 0.1.12.

1. What is CVE-2024-52798? CVE-2024-52798 is a high-severity inefficient regular expression (ReDoS) vulnerability in path-to-regexp (npm), affecting versions < 0.1.12. It is fixed in 0.1.12. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
2. How severe is CVE-2024-52798? CVE-2024-52798 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of path-to-regexp are affected by CVE-2024-52798? path-to-regexp (npm) versions < 0.1.12 is affected.
4. Is there a fix for CVE-2024-52798? Yes. CVE-2024-52798 is fixed in 0.1.12. Upgrade to this version or later.
5. Is CVE-2024-52798 exploitable, and should I be worried? Whether CVE-2024-52798 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-52798 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-52798? Upgrade path-to-regexp to 0.1.12 or later.