CVE-2026-45149

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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
Trending — Patch released this week
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: None knownExposed: 0

A fix is available — apply it.

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. From 5.0.0 to before 5.0.6, the max option was being applied too late. When expanding a single large numeric range like {1..10000000}, the sequence generation loop generates all 10 million intermediate elements before the max limit is applied With max=10, the output is correctly limited to 10 items, but the process still allocates ~505 MB and spends ~800ms building the full intermediate array. This vulnerability is fixed in 5.0.6.

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

Published

May 18, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 10, 2026
Patch available. Sources: github.
github Patch Available

Large numeric range defeats documented `max` DoS protection · Advisory · juliangruber/brace-expansion · GitHub

https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-jxxr-4gwj-5jf2

Vendor Advisories for CVE-2026-45149(13)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17870615542026-08-19redhat
redhatdevspaces/dashboard-rhel9:17847371502026-07-29redhat
redhatllvm21-main-21.1.8-6.hum12026-06-07redhat
redhatrust-main-1.96.0-1.hum12026-06-03redhat
redhatnodejs26-main-26.3.0-1.2.hum12026-06-02redhat
redhatdotnet8-0-main-8.0.127-1.hum12026-05-14redhat
redhatnodejs24-main-24.15.0-1.hum12026-05-05redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat
redhatllvm-main-21.1.8-1.1.hum12026-04-11redhat
redhatyarnpkg-main-1.22.22-18.1.hum12026-04-11redhat
redhatnodejs25-main-25.9.0-1.1.hum12026-04-10redhat
redhatnodejs22-main-22.22.0-1.3.hum12026-04-10redhat

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.0.3+~1.1.2-3 (6 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——
Debian:14(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-22.0.3+~1.1.2-3—
npm(1)
PackageVulnerable rangeFixed inDependents
brace-expansion—5.0.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× 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.

Showing the most recent 100 of 142 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45149?
CVE-2026-45149 is a high vulnerability published on May 18, 2026. The brace-expansion library generates arbitrary strings containing a common prefix and suffix. From 5.0.0 to before 5.0.6, the max option was being applied too late. When expanding a single large numeric range like {1..10000000}, the sequence generation loop generates all 10 million intermediate…
When was CVE-2026-45149 disclosed?
CVE-2026-45149 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45149 actively exploited?
CVE-2026-45149 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 77.3% of all scored CVEs.
What is the CVSS score of CVE-2026-45149?
CVE-2026-45149 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45149, 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-45149

Explore →

Is Your Infrastructure Affected by CVE-2026-45149?

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

Start Free Scan →Browse All CVEs