Skip to content
Noroxi
NVD / CVE Program· CNA openjs

CVE-2026-4867: path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: path-to-regexp path-to-regexp 0.1.13.

Low priority for now. Upgrade to path-to-regexp path-to-regexp 0.1.13 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Mar 26, 2026
Updated
Jun 17, 2026
EPSS
0.5% · 43th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · openjs
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-4867

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for pillarjs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
pillarjspath-to-regexp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • pillarjs path-to-regexpbefore 0.1.13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.

  • path-to-regexp path-to-regexp

    • before 0.1.13affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12node-path-to-regexpbefore 1.0.1-11.0.1-1
npmpath-to-regexpfrom 0.2.0 · before 1.9.01.9.0
npmpath-to-regexpfrom 2.0.0 · before 3.3.03.3.0
npmpath-to-regexpfrom 4.0.0 · before 6.3.06.3.0
npmpath-to-regexpfrom 7.0.0 · before 8.0.08.0.0
npmpath-to-regexpbefore 0.1.130.1.13
npmpath-to-regexpbefore 0.1.100.1.10

Same product

pillarjs: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-4926path-to-regexp vulnerable to Denial of Service via sequential optional groups
    30Monitor
  • CVE-2024-52798path-to-regexp Unpatched `path-to-regexp` ReDoS in 0.1.x
    30Monitor
  • CVE-2024-45296path-to-regexp outputs backtracking regular expressions
    30Monitor

Published before and after this one in the same product

  • Later →CVE-2026-4923Mar 26, 2026 · path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
path-to-regexp path-to-regexp0.1.13Vendor (CNA)
debian:node-path-to-regexp1.0.1-1 · Debian:12Package registry (OSV)
npm:path-to-regexp0.1.10Package registry (OSV)
npm:path-to-regexp0.1.13Package registry (OSV)
npm:path-to-regexp1.9.0Package registry (OSV)
npm:path-to-regexp3.3.0Package registry (OSV)
npm:path-to-regexp6.3.0Package registry (OSV)
npm:path-to-regexp8.0.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-52798476 days apartpath-to-regexp Unpatched `path-to-regexp` ReDoS in 0.1.x
    30Monitor
  • CVE-2026-49230 days apartpath-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-1333 · Inefficient Regular Expression Complexity

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records