Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V2 - Validation and Business Logic Regex complexity limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS 5.9 score (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) indicates a medium-severity availability impact requiring high attack complexity and unauthenticated remote access. The AV:N (network) and PR:N (no privileges required) signals demonstrate broad exploitability from the network without authentication. However, the AC:H (high complexity) modifier is significant-successful exploitation requires the application to be deployed with a specifically vulnerable path pattern configuration (multiple wildcards with non-terminal positioning), and the attacker must craft matching input that triggers the backtracking condition. The availability-only impact (A:H with C:N/I:N) limits scope to denial of service rather than confidentiality or integrity breach. Real-world risk depends on deployment patterns: applications using simple routing (single wildcards, terminal wildcards, or single parameters) are unaffected; only those matching the unsafe examples provided are at risk. The requirement for specific path configuration patterns and attack input significantly reduces the attack surface compared to the raw CVSS score suggests. EPSS data was not provided in the source data; patch availability (version 8.4.0) is confirmed, lowering ongoing risk for organizations that can upgrade promptly. |
| Exploit ScenarioDerived | An attacker identifies an application using path-to-regexp 8.0.0-8.3.x with a route definition vulnerable to the ReDoS pattern, such as a file serving endpoint defined as /:type/*path-:format. The attacker sends a specially crafted HTTP request with a path component engineered to trigger catastrophic regex backtracking (e.g., a long string of repeated characters matching the prefix but failing at the end of the pattern). The regex engine enters exponential backtracking, consuming CPU resources and causing the application to become unresponsive to legitimate requests. This requires no authentication or user interaction, and the attack can be repeated to sustain denial of service. The AC:H complexity rating reflects that the attacker must identify or guess the specific vulnerable route pattern and construct matching input; however, once a vulnerable pattern is discovered, exploitation is trivial. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
path-to-regexp versions prior to 8.4.0 are vulnerable to Regular Expression Denial of Service (ReDoS) when processing multiple wildcard parameters combined with path parameters in specific configurations. Unauthenticated remote attackers can craft malicious path patterns containing multiple wildcards (not at the end) to trigger catastrophic regex backtracking, causing denial of service against applications using the affected library. No public exploit code or active exploitation has been confirmed at time of analysis.
RemediationAI
Upgrade path-to-regexp to version 8.4.0 or later immediately. This patched version resolves the regex generation logic to prevent ReDoS exploitation. Applications cannot perform in-place updates via configuration; a dependency upgrade is required. Until patching is possible, conduct an audit of application routing configurations to identify and eliminate unsafe path patterns matching the listed examples (/*foo-*bar-:baz, /*a-:b-*c-:d, /x/*a-:b/*c/y); refactor affected routes to use safe patterns such as /*foo-:bar or /*foo-:bar-*baz (with wildcards only at terminal positions). As a verification step before and after remediation, test the application's routing regex output using the ReCheck playground (https://makenowjust-labs.github.io/recheck/playground/) to confirm vulnerability status. Network-level mitigations such as request timeout enforcement and rate limiting on routing endpoints can provide defense-in-depth but do not eliminate the underlying flaw.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
path-to-regexp is a JavaScript library that converts URL path strings into regular expressions for routing purposes, commonly used in Express.js and other Node.js web frameworks. The vulnerability (CWE-1333: Improper Restriction of Rendered UI Layers or Frames) stems from how the library generates regex patterns when processing path definitions containing multiple wildcard operators (asterisks) combined with named parameters (colons). When wildcards appear in non-terminal positions followed by additional parameters, the generated regex exhibits polynomial time complexity due to excessive backtracking during pattern matching. The affected product range is path-to-regexp versions 8.0.0 through 8.3.x, as confirmed via CPE (cpe:2.3:a:path-to-regexp:path-to-regexp:*:*:*:*:*:*:*:*) and EUVD tracking (EUVD-2026-16322). The library's regex generation logic fails to account for pathological input patterns that trigger nested quantifier backtracking scenarios.
Know when Path To Regexp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
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.
Blast Radius
ecosystem impact- 32 npm packages depend on path-to-regexp (12 direct, 20 indirect)
Ecosystem-wide dependent count for version 8.0.0.
Executive ViewAI
CVE-2026-4923 presents moderate security risk rated CVSS 5.9. Exploitation could compromise the security of affected deployments. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Path To Regexp
View allThe path-to-regexp library versions 8.0.0 through 8.3.0 suffer from catastrophic regular expression denial of service vi
Catastrophic backtracking in path-to-regexp versions prior to 0.1.13 enables remote denial of service attacks through sp
Same technique Denial Of Service
View allVendor StatusVendor
Debian
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye | vulnerable | 6.2.0-1 | - |
| bookworm | vulnerable | 6.2.1-1 | - |
| trixie | vulnerable | 6.3.0-1 | - |
| forky, sid | vulnerable | 8.3.0-1 | - |
| (unstable) | fixed | (unfixed) | - |
EUVD-2026-16322
GHSA-27v5-c462-wpq7
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB