CVE-2026-25547

CRITICALNVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

@isaacs/brace-expansion is a hybrid CJS/ESM TypeScript fork of brace-expansion. Prior to version 5.0.1, @isaacs/brace-expansion is vulnerable to a denial of service (DoS) issue caused by unbounded brace range expansion. When an attacker provides a pattern containing repeated numeric brace ranges, the library attempts to eagerly generate every possible combination synchronously. Because the expansion grows exponentially, even a small input can consume excessive CPU and memory and may crash the Node.js process. This issue has been patched in version 5.0.1.

CVSS v3
9.2
EG Score
9.2(medium)
EG Risk
57(Track)
EG Risk 57/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
Severity92% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

February 4, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Uncontrolled Resource Consumption in @isaacs/brace-expansion · Advisory · isaacs/brace-expansion · GitHub

https://github.com/isaacs/brace-expansion/security/advisories/GHSA-7h2j-956f-4vf2

Vendor Advisories for CVE-2026-25547(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:22-9060020260409121057.rhel92026-04-14redhat
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs22-1:22.22.2-2.el10_02026-04-09redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat
redhatnodejs:22-9070020260401095228.rhel92026-04-09redhat
redhatnodejs:22-8100020260331102257.6d8804032026-04-08redhat
redhatnodejs22-1:22.22.2-1.el10_12026-04-08redhat

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-brace-expansion2.0.0-1 ... 2.0.3+~1.1.2-3 (8 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-brace-expansion2.0.1+~1.1.0-1 ... 2.1.4+~1.1.2-1 (7 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-brace-expansion2.0.1+~1.1.0-2, 2.0.3+~1.1.2-1, 2.0.3+~1.1.2-2, 2.0.3+~1.1.2-3, 2.1.4+~1.1.2-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-brace-expansion2.0.1+~1.1.0-2, 2.0.3+~1.1.2-12.0.3+~1.1.2-2—
npm(1)
PackageVulnerable rangeFixed inDependents
@isaacs/brace-expansion—5.0.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× 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 198 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25547?
CVE-2026-25547 is a critical vulnerability published on February 4, 2026. @isaacs/brace-expansion is a hybrid CJS/ESM TypeScript fork of brace-expansion. Prior to version 5.0.1, @isaacs/brace-expansion is vulnerable to a denial of service (DoS) issue caused by unbounded brace range expansion. When an attacker provides a pattern containing repeated numeric brace ranges,…
When was CVE-2026-25547 disclosed?
CVE-2026-25547 was first published in the National Vulnerability Database on February 4, 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-25547 actively exploited?
CVE-2026-25547 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 58.2% of all scored CVEs.
What is the CVSS score of CVE-2026-25547?
CVE-2026-25547 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-25547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25547, 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-25547

Explore →

Is Your Infrastructure Affected by CVE-2026-25547?

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

Start Free Scan →Browse All CVEs