CVE-2026-4867
Last modified
CVE-2026-4867 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. EPSS estimates a 0.50% chance of exploitation in the next 30 days.
Description
Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. The backtrack protection added in path-to-regexp@0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, so capture groups overlap and cause catastrophic backtracking. Patches: Upgrade to path-to-regexp@0.1.13 Custom regex patterns in route definitions (e.g., /:a-:b([^-/]+)-:c([^-/]+)) are not affected because they override the default capture group. Workarounds: All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b-:c to /:a-:b([^-/]+)-:c([^-/]+). If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Pillarjs | Path-To-Regexp | < 0.1.13 |
References
- https://blakeembrey.com/posts/2024-09-web-redosTechnical Description
- https://cna.openjsf.org/security-advisories.htmlThird Party Advisory
- https://github.com/advisories/GHSA-9wv6-86v2-598jNot Applicable
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-4867?
How severe is CVE-2026-4867?
How do I fix CVE-2026-4867?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-48615A flaw in Node.js proxy tunnel error handling could expose p…7.5
- CVE-2026-48616Rocket.Chat versions <8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0…9.3
- CVE-2026-48617A flaw in Node.js Permission Model enforcement allows Bypass…1.8
- CVE-2026-48618A flaw in Node.js TLS hostname handling can cause Node.js un…6.5
- CVE-2026-48619A flaw in Node.js HTTP/2 client allows a server to send an u…7.5
- CVE-2026-4862A security vulnerability has been detected in UTT HiPER 1250…8.8
- CVE-2026-4868GitLab has remediated an issue in GitLab EE affecting all ve…8.2
- CVE-2026-48681OpenStack Ironic through before 35.0.2 allows file overwrite…8.1
- CVE-2026-48682FastNetMon Community Edition through 1.2.9 contains an out-o…5.9
- CVE-2026-48683FastNetMon Community Edition through 1.2.9 contains an out-o…6.5
- CVE-2026-48684FastNetMon Community Edition through 1.2.9 contains an out-o…6.5
- CVE-2026-48685FastNetMon Community Edition through 1.2.9 has out-of-bounds…6.5
Are you affected by CVE-2026-4867?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
