Bump path-to-regexp from 8.3.0 to 8.4.2 in /sandbox
Open
Number: #343
Type: Pull Request
State: Open
Type: Pull Request
State: Open
Author:
dependabot[bot]
Association: Unknown
Comments: 2
Association: Unknown
Comments: 2
Created:
April 10, 2026 at 12:55 PM UTC
(4 months ago)
(4 months ago)
Updated:
April 10, 2026 at 01:44 PM UTC
(4 months ago)
(4 months ago)
Labels:
dependencies javascript
dependencies javascript
Description:
Bumps path-to-regexp from 8.3.0 to 8.4.2.
Release notes
Sourced from path-to-regexp's releases.
v8.4.2
Fixed
- Error on trailing backslash (#434) 9a78879
Performance
- Minimize array allocations (#437) 937c02d
- Improve compile performance (#436) 57247e6
- Should improve compilation performance by ~25%
- Remove internal tokenization during parse (#435) 5844988
- Should improve parse performance by ~20%
Bundle size to 1.93 kB, from 1.97 kB.
https://github.com/pillarjs/path-to-regexp/compare/v8.4.1...v8.4.2
v8.4.1
Fixed
- Remove trie deduplication (#431) 6bc8e84
- Using a trie required non-greedy matching, which regressed wildcards in non-ending mode by matching them up until the first match. For example:
/*foowith/a/b=/a/*foo.htmlwith/a/b.html/c.html=/a/b.html- Allow backtrack handling to match itself (#427) 5bcd30b
- When backtracking was introduced, it rejected matching things like
/:"a"_:"b"against/foo__. This makes intuitive sense because the second parameter is not going to backtrack on_anymore, but it's somewhat unexpected since there's no reason it shouldn't match the second_.
https://github.com/pillarjs/path-to-regexp/compare/v8.4.0...v8.4.1
v8.4.0
Important
Fixed
- Restricts wildcard backtracking when using more than 1 in a path (pillarjs/path-to-regexp#421)
Changed
- Dedupes regex prefixes (pillarjs/path-to-regexp#422)
- This will result in shorter regular expressions for some cases using optional groups
- Rejects large optional route combinations (pillarjs/path-to-regexp#424)
- When using groups such as
/users{/delete}it will restrict the number of generated combinations to < 256, equivalent to 8 top-level optional groups and unlikely to occur in a real world application, but avoids exploding the regex size for applications that accept user created routes
Commits
cbf30258.4.2937c02dMinimize array allocations (#437)57247e6Improve compile performance (#436)5844988Remove internal tokenization during parse (#435)9a78879Error on trailing backslash (#434)7f058768.4.16bc8e84Remove trie deduplication (#431)5bcd30bAllow backtrack handling to match itself (#427)9f9c6c5Add parsing to benchmarks (#418)9fd31e0Addtrailing: falsetests (#428)- Additional commits viewable in compare view
Package Dependencies
Package:
path-to-regexp
Ecosystem:
npm
npm
Version Change:
8.3.0 → 8.4.2
Update Type:
Minor
Minor
Path:
/sandbox
Security Advisories
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
GHSA-27v5-c462-wpq7
CVE-2026-4923
MODERATE
### 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 seco...
path-to-regexp vulnerable to Denial of Service via sequential optional groups
GHSA-j3q9-mxjg-w52f
CVE-2026-4926
HIGH
### 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...
Technical Details
| ID: | 15192150 |
| UUID: | 4239286201 |
| Node ID: | PR_kwDOEeBrKM7Rc31q |
| Host: | GitHub |
| Repository: | NHSDigital/nhs-app-api |