CVE-2026-26996

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% 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: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions 10.2.0 and below are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS. This issue has been fixed in version 10.2.1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

February 20, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

ReDoS via repeated wildcards with non-matching literal in pattern · Advisory · isaacs/minimatch · GitHub

https://github.com/isaacs/minimatch/security/advisories/GHSA-3ppc-4f35-3m26
github_commit

commit 2e111f3a79ab (isaacs/minimatch)

Fix landed in isaacs/minimatch commit 2e111f3a79ab — awaiting tagged release

https://github.com/isaacs/minimatch/commit/2e111f3a79abc00fa73110195de2c0f2351904f5

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsatellite/iop-host-inventory-frontend-rhel9:17859227642026-08-06redhat
redhatopenshift4/ose-console-rhel9:17848033442026-08-06redhat
redhatmta/mta-ui-rhel9:17851690132026-08-04redhat
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatopenshift4/ose-console-rhel9:17833067152026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatopenshift4/ose-console-rhel9:17834531362026-07-15redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17810324952026-06-16redhat
redhatsatellite/iop-advisor-frontend-rhel9:17811816732026-06-16redhat
redhatopenshift4/ose-console-rhel9:17803654212026-06-10redhat
redhatautomation-gateway-0:2.5.20260422-3.el9ap2026-06-09redhat
redhatopenshift4/ose-console-rhel9:17798743962026-06-03redhat
redhatopenshift4/ose-console-rhel9:17798672382026-06-02redhat
redhatdevspaces/openvsx-rhel9:17795282242026-05-28redhat
redhatorg.keycloak-keycloak-parent2026-05-18redhat
redhateap8-wildfly-0:8.1.6-5.GA_redhat_00007.1.el8eap2026-05-18redhat
redhatautomation-platform-ui-0:2.6.8-1.el9ap2026-05-04redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17763192752026-04-23redhat
redhatnodejs:20-9060020260422064119.rhel92026-04-22redhat
redhatnodejs:20-9040020260421133644.rhel92026-04-22redhat
redhatrhdh/rhdh-hub-rhel9:17767842862026-04-22redhat
redhatnodejs:20-8100020260414073138.489197e62026-04-15redhat
redhatnodejs:22-9060020260409121057.rhel92026-04-14redhat
redhatnodejs:20-9070020260409073121.rhel92026-04-13redhat
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs:24-8100020260408131901.6d8804032026-04-13redhat
redhatnodejs:22-9070020260401095228.rhel92026-04-09redhat
redhatnodejs22-1:22.22.2-2.el10_02026-04-09redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat

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 rangeFixed inDependents
node-minimatch3.0.4+~3.0.3-1 ... 9.0.7-1 (17 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-minimatch5.1.1+~5.1.2-1 ... 9.0.7-2 (9 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-minimatch9.0.3-6, 9.0.7-1, 9.0.7-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-minimatch9.0.3-69.0.7-1
npm(1)
PackageVulnerable rangeFixed inDependents
minimatch3.1.3

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 6× in last 7d / 32× 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.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-10 09:34 UTCEPSS rescore
  3. 2026-09-08 22:00 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 14:11 UTCEPSS rescore
  9. 2026-09-01 13:53 UTCEPSS rescore
  10. 2026-09-01 04:39 UTCEPSS rescore
  11. 2026-08-31 17:34 UTCOSV refresh
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:48 UTCEPSS rescore
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 17:03 UTCEPSS rescore
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 40 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 21:44 UTCVendor advisory
  3. 2026-08-14 09:30 UTCEG score recompute
  4. 2026-08-14 09:30 UTCVendor advisory
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 01:39 UTCEG score recompute
  7. 2026-08-13 01:39 UTCVendor advisory
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 01:55 UTCEG score recompute
  10. 2026-08-12 01:55 UTCVendor advisory
  11. 2026-08-11 13:42 UTCEPSS rescore
  12. 2026-08-11 07:02 UTCEG score recompute
  13. 2026-08-11 07:02 UTCVendor advisory
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 09:28 UTCVendor advisory
  16. 2026-08-09 20:42 UTCEG score recompute
  17. 2026-08-09 20:42 UTCVendor advisory
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 09:06 UTCEG score recompute
  20. 2026-08-09 09:06 UTCVendor advisory
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-08 08:55 UTCVendor advisory
  23. 2026-08-07 21:20 UTCEG score recompute
  24. 2026-08-07 21:20 UTCVendor advisory
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-06 03:23 UTCEG score recompute
  27. 2026-08-06 03:23 UTCVendor advisory
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 20:03 UTCEG score recompute 1.20
  32. 2026-08-02 20:03 UTCVendor advisory
  33. 2026-08-02 02:26 UTCEPSS rescore
  34. 2026-08-01 04:16 UTCEPSS rescore
  35. 2026-07-30 16:27 UTCEPSS rescore
  36. 2026-07-30 01:30 UTCEPSS rescore
  37. 2026-07-28 15:36 UTCEPSS rescore
  38. 2026-07-27 12:55 UTCEG score recompute
  39. 2026-07-27 12:55 UTCVendor advisory
  40. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-26996?
CVE-2026-26996 is a high vulnerability published on February 20, 2026. minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions 10.2.0 and below are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive wildcards followed by a literal character that doesn't…
When was CVE-2026-26996 disclosed?
CVE-2026-26996 was first published in the National Vulnerability Database on February 20, 2026, with the most recent update on June 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-26996 actively exploited?
CVE-2026-26996 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.5% of all scored CVEs.
What is the CVSS score of CVE-2026-26996?
CVE-2026-26996 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-26996?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26996, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-26996?

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