CVE-2026-13149

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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 week
7.7EG
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.7Exploit: None knownExposed: 0

A fix is available — apply it.

brace-expansion through 5.0.6 is vulnerable to denial of service. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace groups. An attacker who passes a crafted string to expand(), directly or transitively, can cause significant CPU consumption and event-loop blocking. The max option does not mitigate this, as it bounds the output size rather than the recursion work.

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

Published

June 30, 2026

Last Modified

July 8, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit c7e33ec13ac1 (juliangruber/brace-expansion)

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

https://github.com/juliangruber/brace-expansion/commit/c7e33ec13ac1a684c116720843ce24e208611754

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs26-main-26.5.0-1.4.hum12026-07-24redhat
redhatansible-automation-platform/automation-portal:17846229512026-07-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatdotnet8-0-main-8.0.128-1.1.hum12026-07-10redhat
redhatnodejs22-main-22.23.1-2.hum12026-07-03redhat
redhatnodejs24-main-24.18.0-0.2.hum12026-07-01redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat

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-expansion2.1.2

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 67× 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-07-27 01:21 UTCEG score recompute
  2. 2026-07-27 01:21 UTCVendor advisory
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 13:56 UTCEG score recompute
  6. 2026-07-26 13:56 UTCVendor advisory
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:05 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:30 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-17 02:20 UTCVendor advisory
  18. 2026-07-16 17:02 UTCEPSS rescore
  19. 2026-07-16 14:56 UTCVendor advisory
  20. 2026-07-16 03:18 UTCVendor advisory
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 15:55 UTCVendor advisory
  23. 2026-07-15 04:31 UTCVendor advisory
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-14 16:52 UTCVendor advisory
Show 42 more
  1. 2026-07-14 05:29 UTCVendor advisory
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 18:06 UTCVendor advisory
  4. 2026-07-13 06:42 UTCVendor advisory
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-12 19:19 UTCVendor advisory
  7. 2026-07-12 07:56 UTCVendor advisory
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 20:33 UTCVendor advisory
  10. 2026-07-11 09:09 UTCVendor advisory
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-10 21:46 UTCVendor advisory
  13. 2026-07-10 10:23 UTCVendor advisory
  14. 2026-07-09 22:59 UTCVendor advisory
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 11:36 UTCVendor advisory
  17. 2026-07-09 00:09 UTCVendor advisory
  18. 2026-07-08 12:45 UTCVendor advisory
  19. 2026-07-08 01:17 UTCVendor advisory
  20. 2026-07-07 13:53 UTCVendor advisory
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-07 02:29 UTCVendor advisory
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 15:05 UTCVendor advisory
  25. 2026-07-06 03:36 UTCVendor advisory
  26. 2026-07-06 02:23 UTCEPSS rescore
  27. 2026-07-05 16:12 UTCVendor advisory
  28. 2026-07-05 04:47 UTCVendor advisory
  29. 2026-07-05 02:30 UTCEPSS rescore
  30. 2026-07-05 02:30 UTCEPSS rescore
  31. 2026-07-04 17:13 UTCVendor advisory
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-04 05:49 UTCVendor advisory
  34. 2026-07-03 18:21 UTCVendor advisory
  35. 2026-07-03 06:58 UTCVendor advisory
  36. 2026-07-02 19:30 UTCVendor advisory
  37. 2026-07-02 08:06 UTCVendor advisory
  38. 2026-07-01 15:06 UTCEPSS rescore
  39. 2026-07-01 15:06 UTCEPSS rescore
  40. 2026-06-30 23:22 UTCEPSS rescore
  41. 2026-06-30 10:32 UTCEG score recompute
  42. 2026-06-30 10:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-13149?
CVE-2026-13149 is a high vulnerability published on June 30, 2026. brace-expansion through 5.0.6 is vulnerable to denial of service. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace groups. An attacker who passes a crafted string to expand(), directly or transitively, can cause significant CPU…
When was CVE-2026-13149 disclosed?
CVE-2026-13149 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13149 actively exploited?
CVE-2026-13149 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 80.0% of all scored CVEs.
What is the CVSS score of CVE-2026-13149?
CVE-2026-13149 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-13149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13149, 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-13149

Explore →

Is Your Infrastructure Affected by CVE-2026-13149?

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