CVE-2026-4926

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:openjs, epss
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

Published

March 26, 2026

Last Modified

September 17, 2026

Advisory Details (10)

Auto-updated Jul 1, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:24761
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19410
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19409
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:17789
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:13826
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:13545
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10175
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10172
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10153
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Patch Availability(18)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-path-to-regexp6.2.0-1 ... 8.4.2-1 (9 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-path-to-regexp6.2.1-1 ... 8.4.2-1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-path-to-regexp6.3.0-1, 8.3.0-1, 8.4.0-1, 8.4.1-1, 8.4.2-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-path-to-regexp6.3.0-1, 8.3.0-1
  • every version up to 8.4.0-1: fixed in 8.4.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
path-to-regexp—
  • 8.0.0 up to 8.4.0: fixed in 8.4.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 231 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-07 06:24 UTCOSV refresh
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 00:27 UTCEPSS rescore
  15. 2026-09-23 17:53 UTCEPSS rescore
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-17 12:11 UTCEG score recompute
  19. 2026-09-17 12:11 UTCVendor advisory
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-14 12:35 UTCEG score recompute
  23. 2026-09-14 12:35 UTCVendor advisory
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-09 13:42 UTCEG score recompute
  3. 2026-09-09 13:42 UTCVendor advisory
  4. 2026-09-09 12:40 UTCEG score recompute
  5. 2026-09-09 12:40 UTCVendor advisory
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-07 14:01 UTCEG score recompute
  9. 2026-09-07 14:01 UTCVendor advisory
  10. 2026-09-07 13:18 UTCEG score recompute
  11. 2026-09-07 13:18 UTCVendor advisory
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 13:25 UTCEG score recompute
  24. 2026-08-25 13:25 UTCVendor advisory
  25. 2026-08-25 12:22 UTCEG score recompute
  26. 2026-08-25 12:22 UTCVendor advisory
  27. 2026-08-24 13:31 UTCEG score recompute
  28. 2026-08-24 13:31 UTCVendor advisory
  29. 2026-08-24 12:27 UTCEG score recompute
  30. 2026-08-24 12:27 UTCVendor advisory
  31. 2026-08-23 00:19 UTCEPSS rescore
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-20 22:55 UTCEPSS rescore
  34. 2026-08-19 17:04 UTCEPSS rescore
  35. 2026-08-19 12:28 UTCEG score recompute
  36. 2026-08-19 12:28 UTCVendor advisory
  37. 2026-08-19 12:12 UTCEG score recompute
  38. 2026-08-19 12:12 UTCVendor advisory
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-18 12:21 UTCEG score recompute
  41. 2026-08-18 12:21 UTCVendor advisory
  42. 2026-08-17 13:47 UTCEPSS rescore
  43. 2026-08-17 12:25 UTCEG score recompute
  44. 2026-08-17 12:25 UTCVendor advisory
  45. 2026-08-17 12:13 UTCEG score recompute
  46. 2026-08-17 12:13 UTCVendor advisory
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 10:06 UTCEG score recompute
  49. 2026-08-16 10:06 UTCVendor advisory
  50. 2026-08-16 02:14 UTCEPSS rescore
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 19:26 UTCVendor advisory
  53. 2026-08-14 06:24 UTCEG score recompute
  54. 2026-08-14 06:24 UTCVendor advisory
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-12 20:41 UTCEG score recompute
  57. 2026-08-12 20:41 UTCVendor advisory
  58. 2026-08-12 13:51 UTCEPSS rescore
  59. 2026-08-11 20:48 UTCEG score recompute
  60. 2026-08-11 20:48 UTCVendor advisory
  61. 2026-08-11 03:50 UTCEG score recompute
  62. 2026-08-11 03:50 UTCVendor advisory
  63. 2026-08-11 00:00 UTCEPSS rescore
  64. 2026-08-10 12:27 UTCEG score recompute
  65. 2026-08-10 12:27 UTCVendor advisory
  66. 2026-08-10 05:20 UTCVendor advisory
  67. 2026-08-09 17:39 UTCEG score recompute
  68. 2026-08-09 17:39 UTCVendor advisory
  69. 2026-08-09 13:46 UTCEPSS rescore
  70. 2026-08-09 05:57 UTCEG score recompute
  71. 2026-08-09 05:57 UTCVendor advisory
  72. 2026-08-08 16:37 UTCEPSS rescore
  73. 2026-08-08 04:03 UTCEG score recompute
  74. 2026-08-08 04:03 UTCVendor advisory
  75. 2026-08-07 16:23 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-4926?
CVE-2026-4926 is a high vulnerability published on March 26, 2026. 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…
When was CVE-2026-4926 disclosed?
CVE-2026-4926 was first published on March 26, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4926 actively exploited?
CVE-2026-4926 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4926?
CVE-2026-4926 has a CVSS base score of 7.5 (the CNA's own assessment, by openjs; NVD's own analysis pending).
How do I remediate CVE-2026-4926?
A fix for CVE-2026-4926 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4926 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4926

Explore →

Is Your Infrastructure Affected by CVE-2026-4926?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.