CVE-2026-4923: Impact: When using multiple wildcards, combined with at least one parameter, a regular expression can be gene

Q: How do I fix CVE-2026-4923?

path-to-regexp: upgrade to 8.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-4923 being exploited?

CVE-2026-4923 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-4923 affect?

CVE-2026-4923 affects path-to-regexp. Severity is medium (CVSS 5.9). 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

Q: How urgent is CVE-2026-4923?

Priority 33/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-4923 is a medium-severity flaw (CVSS 5.9) affecting path-to-regexp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 par

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-1333
Published	2026-03-26
Last modified	2026-06-17

Publisher (CNA): openjs · Vendor: pillarjs

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-26 19:17 UTCPublished CVE record published
2026-06-17 10:57 UTCUpdated Record last modified

pillarjs path-to-regexp UPGRADE

Affected: >= 8.0.0 and < 8.4.0

Fixed in: 8.4.0

Safe to downgrade to: a release before 8.0.0

1. Check installed version

npm ls path-to-regexp

2. UPGRADE to 8.4.0

npm install path-to-regexp@">=8.4.0"

3. If no update is available yet, DOWNGRADE to a release before 8.0.0

npm view path-to-regexp versions npm install path-to-regexp@"<8.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-4923?

path-to-regexp: upgrade to 8.4.0. Exact commands for each OS are on this page.

Is CVE-2026-4923 being exploited?

CVE-2026-4923 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-4923 affect?

CVE-2026-4923 affects path-to-regexp. Severity is medium (CVSS 5.9). 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

How urgent is CVE-2026-4923?

Priority 33/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-4926 HIGH 7.5 UPGRADE Impact: A bad regular expression is generated any time you have multiple sequential optional groups (curly br
CVE-2026-4867 HIGH 7.5 UPGRADE Impact: A bad regular expression is generated any time you have three or more parameters within a single segm

References

← Back to latest CVEs