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
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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%
EPSS PROB
0.4%
EPSS %ILE
26th
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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
node-brace-expansion2.0.0-1 ... 2.0.3+~1.1.2-3 (8 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-brace-expansion2.0.1+~1.1.0-1 ... 2.1.4+~1.1.2-1 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
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
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-brace-expansion2.0.1+~1.1.0-2, 2.0.3+~1.1.2-1, 2.0.3+~1.1.2-2
  • every version up to 2.0.3+~1.1.2-3: fixed in 2.0.3+~1.1.2-3
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
brace-expansion—
  • 5.0.0 up to 5.0.6: fixed in 5.0.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 21× 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 178 total refreshes for this CVE.

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

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 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.4% probability of exploitation in the next 30 days (26th percentile of EPSS-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?
A fix for CVE-2026-45149 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45149 are linked in the Vendor Advisories panel on this page.

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.