🚨 [security] Update path-to-regexp 8.2.0 → 8.4.0 (minor)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ path-to-regexp (8.2.0 → 8.4.0) · Repo · Changelog

Security Advisories 🚨

🚨 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.

🚨 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 developers are using multiple wildcard parameters, they can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.

Release Notes

8.4.0

Important

• Fix CVE-2026-4926 (GHSA-j3q9-mxjg-w52f)
• Fix CVE-2026-4923 (GHSA-27v5-c462-wpq7)

Fixed

• Restricts wildcard backtracking when using more than 1 in a path (#421)

Changed

• Dedupes regex prefixes (#422)
  • This will result in shorter regular expressions for some cases using optional groups
• Rejects large optional route combinations (#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

8.3.0

Changed

• Add custom error class (#398) 2a7f2a4
• Allow plain objects for TokenData (#391) 687a9bb
• Escape text should escape backslash (#390) a4a8552
• Improved error messages and stack size (#363) a6bdf40

Other

• Minifying the parser
  • PR (#401) 9df2448
  • PR (#395) 4a91505
  • Shaving some bytes d63f44b
  • Remove optional operator 973d15c

v8.2.0...v8.3.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 28 commits:

• 8.4.0
• Reject large optional route combinations (#424)
• Byte optimization (#423)
• Dedupe regex prefixes (#422)
• Restrict repeated wildcard backtracking (#421)
• Remove dependabot config (#404)
• Remove `package-lock.json` (#407)
• 8.3.0
• Move parameter name errors up in docs (#402)
• Remove more bytes from parser (#401)
• Bump actions/checkout from 4 to 5 (#403)
• Remove engines from package (#399)
• Add custom error class (#398)
• 100% test coverage (#396)
• Reduce bytes in parse function (#395)
• Allow plain objects for `TokenData` (#391)
• Escape text should escape backslash (#390)
• Improved error messages and stack size (#363)
• chore: add funding to package.json (#388)
• ci: apply OSSF Scorecard security best practices (#1) (#364)
• Update actions CI workflow (#361)
• Grammar fix in README (#353)
• Add tsbuildinfo to .gitignore (#355)
• upgrade dev deps, node CI/engines, coverage config (#348)
• docs: remove security file (#351)
• Add docs for `pathToRegexp` keys (#340)
• Shaving some bytes
• Remove optional operator

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #601.