CVE-2026-13149

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-20) is not newer than that change (2026-10-25), so it does not.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-40269 (ENISA EUVD) · GHSA-3jxr-9vmj-r5cp (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: None knownExposed services: Not assessed

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

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
Patch available. 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(32)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mod-arch-eval-hub-rhel9:17918612142026-10-19redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17900139052026-09-30redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatrhem/flightctl-ui-rhel9:17894867502026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894881112026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894861812026-09-16redhat
redhatrhem/flightctl-ui-ocp-rhel9:17894864462026-09-16redhat
redhatbrace-expansion2026-09-10redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17876312212026-09-03redhat
redhatsatellite/iop-remediations-rhel9:17882539402026-09-03redhat
redhatsatellite/iop-remediations-rhel9:17882305382026-09-03redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatquay/quay-rhel9:17861819812026-08-12redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17855190172026-08-12redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17855235092026-08-12redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatnodejs22-1:22.23.1-3.el10_02026-08-11redhat
redhatnodejs:22-9060020260804140259.rhel92026-08-10redhat
redhatrhdh/rhdh-hub-rhel9:17859728432026-08-10redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatnodejs-nodemon-0:3.1.14-2.el10_02026-08-10redhat
redhatnodejs26-main-11.19.0-1.26.7.0.1.5.1.hum12026-08-10redhat
npmbrace-expansion @ 5.0.7 (fixes >= 3.0.0, < 5.0.7)—ghsa
npmbrace-expansion @ 1.1.16 (fixes < 1.1.16)—ghsa
npmbrace-expansion @ 2.1.2 (fixes >= 2.0.0, < 2.1.2)—ghsa

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, 2.0.3+~1.1.2-3, 2.1.4+~1.1.2-1
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
brace-expansion—
  • 3.0.0 up to 5.0.7: fixed in 5.0.7
  • every version up to 1.1.16: fixed in 1.1.16
  • 2.0.0 up to 2.1.2: fixed in 2.1.2
—

Weakness Classification(2)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 265 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 165 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-13149?
CVE-2026-13149 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-13149 published?
The CVE record for CVE-2026-13149 was published on June 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-13149 actively exploited?
CVE-2026-13149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13149?
CVE-2026-13149 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-13149?
A fix for CVE-2026-13149 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-13149 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-13149

Explore →

Is Your Infrastructure Affected by CVE-2026-13149?

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