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.4%, top 72% 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.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 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)
EPSS
28.1%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 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(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 35× 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-07 02:29 UTCEG score recompute
  2. 2026-07-07 02:29 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 15:05 UTCEG score recompute
  5. 2026-07-06 15:05 UTCVendor advisory
  6. 2026-07-06 03:36 UTCEG score recompute
  7. 2026-07-06 03:36 UTCVendor advisory
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 16:12 UTCEG score recompute
  10. 2026-07-05 16:12 UTCVendor advisory
  11. 2026-07-05 04:47 UTCEG score recompute
  12. 2026-07-05 04:47 UTCVendor advisory
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 17:13 UTCEG score recompute
  16. 2026-07-04 17:13 UTCVendor advisory
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 05:49 UTCEG score recompute
  19. 2026-07-04 05:49 UTCVendor advisory
  20. 2026-07-03 18:21 UTCEG score recompute
  21. 2026-07-03 18:21 UTCVendor advisory
  22. 2026-07-03 06:58 UTCEG score recompute
  23. 2026-07-03 06:58 UTCVendor advisory
  24. 2026-07-02 19:30 UTCEG score recompute
  25. 2026-07-02 19:30 UTCVendor advisory
Show 10 more
  1. 2026-07-02 08:06 UTCEG score recompute
  2. 2026-07-02 08:06 UTCVendor advisory
  3. 2026-07-01 20:43 UTCEG score recompute
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 09:20 UTCEG score recompute
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 21:55 UTCEG score recompute
  9. 2026-06-30 10:32 UTCEG score recompute
  10. 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. 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 28.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.