CVE-2026-69152

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% 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, secondary
Trending — Patch released this weekElevated
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%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.18, 2.1.4, 3.0.6, and 5.0.9, expand() does not apply maxLength while constructing comma-alternative intermediate arrays or padded sequences, allowing attacker-controlled input to exhaust memory or block the event loop. The fix for CVE-2026-14257 is bypassed by the vulnerability. This issue is fixed in versions 1.1.18, 2.1.4, 3.0.6, and 5.0.9.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 5, 2026

Advisory Details (5)

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

DoS via unbounded intermediate arrays, bypassing the GHSA-mh99-v99m-4gvg mitigation · Advisory · juliangruber/brace-expansion · GitHub

https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-rgw5-rvv9-x895
github_commit

commit cb4b9e47cc2e (juliangruber/brace-expansion)

Fix landed in juliangruber/brace-expansion commit cb4b9e47cc2e — awaiting tagged release

https://github.com/juliangruber/brace-expansion/commit/cb4b9e47cc2ec777c14b2b4492fb431a56f6a031
github_commit

commit 688a99eeaab0 (juliangruber/brace-expansion)

Fix landed in juliangruber/brace-expansion commit 688a99eeaab0 — awaiting tagged release

https://github.com/juliangruber/brace-expansion/commit/688a99eeaab02627c2b89ba8ba4821fecfa659cf
github_commit

commit 1e30c930238d (juliangruber/brace-expansion)

Fix landed in juliangruber/brace-expansion commit 1e30c930238d — awaiting tagged release

https://github.com/juliangruber/brace-expansion/commit/1e30c930238d7162802d88a94189182def178dac
github_commit

commit 139d015104e7 (juliangruber/brace-expansion)

Fix landed in juliangruber/brace-expansion commit 139d015104e7 — awaiting tagged release

https://github.com/juliangruber/brace-expansion/commit/139d015104e71433ad52a41d19467c48ecbb2c7d

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdiscovery/discovery-ui-rhel9:17866348252026-08-13redhat
redhatnodejs24-main-24.18.1-0.2.1.hum12026-08-12redhat
redhatnodejs26-main-26.7.0-1.5.2.hum12026-08-12redhat
redhatnodejs22-main-22.23.2-2.3.2.hum12026-08-12redhat
redhatnodejs-nodemon-0:3.1.14-3.el10_22026-08-10redhat
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatgrafana12-4-main-12.4.6-0.4.hum12026-08-04redhat
redhatgrafana13-1-main-13.1.1-0.5.1.hum12026-08-04redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
brace-expansion5.0.9

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 47× 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-08-15 14:24 UTCVendor advisory
  2. 2026-08-15 02:26 UTCEG score recompute
  3. 2026-08-15 02:26 UTCVendor advisory
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 14:28 UTCVendor advisory
  6. 2026-08-14 02:31 UTCEG score recompute
  7. 2026-08-14 02:31 UTCVendor advisory
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 14:32 UTCVendor advisory
  10. 2026-08-13 02:34 UTCVendor advisory
  11. 2026-08-12 14:37 UTCEG score recompute
  12. 2026-08-12 14:37 UTCVendor advisory
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-12 02:39 UTCVendor advisory
  15. 2026-08-11 14:41 UTCEG score recompute
  16. 2026-08-11 14:41 UTCVendor advisory
  17. 2026-08-11 02:44 UTCEG score recompute
  18. 2026-08-11 02:44 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 14:46 UTCVendor advisory
  21. 2026-08-10 02:48 UTCVendor advisory
  22. 2026-08-09 14:50 UTCEG score recompute
  23. 2026-08-09 14:50 UTCVendor advisory
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-09 02:53 UTCEG score recompute
Show 22 more
  1. 2026-08-09 02:53 UTCVendor advisory
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-08 14:55 UTCVendor advisory
  4. 2026-08-08 02:57 UTCEG score recompute
  5. 2026-08-08 02:57 UTCVendor advisory
  6. 2026-08-07 14:59 UTCVendor advisory
  7. 2026-08-07 03:01 UTCVendor advisory
  8. 2026-08-06 15:04 UTCEG score recompute
  9. 2026-08-06 15:04 UTCVendor advisory
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-06 03:04 UTCEG score recompute
  12. 2026-08-06 03:04 UTCVendor advisory
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 15:06 UTCVendor advisory
  16. 2026-08-04 21:53 UTCEG score recompute
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 09:55 UTCEG score recompute
  19. 2026-08-03 21:20 UTCEG score recompute
  20. 2026-08-03 20:43 UTCEG score recompute
  21. 2026-08-03 17:38 UTCEG score recompute
  22. 2026-08-03 17:09 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-69152?
CVE-2026-69152 is a high vulnerability published on August 3, 2026. The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.18, 2.1.4, 3.0.6, and 5.0.9, expand() does not apply maxLength while constructing comma-alternative intermediate arrays or padded sequences, allowing attacker-controlled input to exhaust…
When was CVE-2026-69152 disclosed?
CVE-2026-69152 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69152 actively exploited?
CVE-2026-69152 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.9% of all scored CVEs.
What is the CVSS score of CVE-2026-69152?
CVE-2026-69152 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-69152?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69152, 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-69152

Explore →

Is Your Infrastructure Affected by CVE-2026-69152?

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