p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de path-to-regexp

Vulnérabilité publiée pour path-to-regexp au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 4

  1. CVE-2026-4923

    Moyenne · CVSS 5.9EPSS 0,36%Correctif disponible

    path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards

    Impact: 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. Unsafe examples: /*foo-*bar-:baz /*a-:b-*c-:d /x/*a-:b/*c/y Safe examples: /*foo-:bar /*foo-:bar-*baz Patches: Upgrade to version 8.4.0. Workarounds: If you are using multiple wildcard parameters, you can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.

    • Mettez à jour vers 8.4.0
    Publication Mise à jour
  2. CVE-2026-4926

    Élevée · CVSS 7.5EPSS 0,8%Correctif disponible

    path-to-regexp vulnerable to Denial of Service via sequential optional groups

    Impact: A bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as `{a}{b}{c}:z`. The generated regex grows exponentially with the number of groups, causing denial of service. Patches: Fixed in version 8.4.0. Workarounds: Limit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns.

    • Mettez à jour vers 8.4.0
    Publication Mise à jour
  3. CVE-2024-52798

    Élevée · CVSS 7.7EPSS 0,79%Correctif disponible

    path-to-regexp Unpatched `path-to-regexp` ReDoS in 0.1.x

    path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. The regular expression that is vulnerable to backtracking can be generated in the 0.1.x release of path-to-regexp. Upgrade to 0.1.12. This vulnerability exists because of an incomplete fix for CVE-2024-45296.

    • Mettez à jour vers 0.1.12
    Publication Mise à jour
  4. CVE-2024-45296

    Élevée · CVSS 7.5EPSS 0,93%Correctif disponible

    path-to-regexp outputs backtracking regular expressions

    path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.

    • Mettez à jour vers 0.1.10
    • Mettez à jour vers 0.1.13
    • Mettez à jour vers 1.9.0
    • Mettez à jour vers 3.3.0
    • Mettez à jour vers 6.3.0
    • Mettez à jour vers 8.0.0
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →