CVE-2026-102276

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-29. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-88550 (ENISA EUVD) · GHSA-6j4f-fj2g-mc7p (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.5%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. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
43rd
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Sep 28, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit 6735c94873ca (juliangruber/brace-expansion)

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

https://github.com/juliangruber/brace-expansion/commit/6735c94873ca570bcdd6a0690033bdd3126379d3
GitHub commit

commit 5171e681c092 (juliangruber/brace-expansion)

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

https://github.com/juliangruber/brace-expansion/commit/5171e681c0922b7ae8bfaf9a331e309107be6edc
GitHub commit

commit 316359e6019c (juliangruber/brace-expansion)

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

https://github.com/juliangruber/brace-expansion/commit/316359e6019c39b3254c8ba8e25dc586a480652c
GitHub commit

commit 0bcbfc0a5928 (juliangruber/brace-expansion)

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

https://github.com/juliangruber/brace-expansion/commit/0bcbfc0a5928c3073d48f42999d1ce4fc1c42fbc
GitHub advisoryMentions a patch (unverified)

DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion · Advisory · juliangruber/brace-expansion · GitHub

https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-6j4f-fj2g-mc7p

Vendor and National Authority Advisories for CVE-2026-102276(20)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(34)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf5/rook-ceph-rhel9-operator:17950755982026-11-20redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17937022752026-11-19redhat
oraclepatch2026-11-17oracle
redhatsatellite/iop-host-inventory-frontend-rhel9:17942341412026-11-13redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17942342222026-11-13redhat
redhatsatellite/iop-advisor-frontend-rhel9:17940170852026-11-13redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17943437432026-11-13redhat
redhatsatellite/iop-advisor-frontend-rhel9:17939621822026-11-13redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17943462832026-11-13redhat
redhatnodejs:24-8100020261105143413.6d8804032026-11-11redhat
redhatnodejs:22-8100020261104150431.6d8804032026-11-11redhat
redhatnodejs:26-9090020261105145947.rhel92026-11-11redhat
redhatcockpit-image-builder-0:110.3-1.el10_32026-11-11redhat
redhatnodejs26-1:26.12.1-3.el10_32026-11-11redhat
redhatrhdh/rhdh-hub-rhel9:17943410432026-11-11redhat
redhatcockpit-image-builder-0:94.5-1.el10_22026-11-11redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:17943112852026-11-10redhat
redhatnodejs24-1:24.22.1-3.el10_22026-11-09redhat
redhatnodejs22-1:22.23.4-1.el10_22026-11-09redhat
redhatnodejs:24-9080020261105135730.rhel92026-11-09redhat
redhatnodejs:22-9080020261103125134.rhel92026-11-09redhat
redhatnodejs-nodemon-0:3.1.14-5.el10_22026-11-09redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17937270322026-11-06redhat
redhatcluster-observability-operator/logging-console-plugin-rhel9:17938392922026-11-05redhat
redhatcluster-observability-operator/logging-console-plugin-rhel9:17936602932026-11-04redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-192026-11-04redhat
redhatrhem/flightctl-ui-rhel9:17937187182026-11-03redhat
redhatrhem/flightctl-ui-rhel10:17937200142026-11-03redhat
redhatnodejs:24-8100020261027151919.6d8804032026-10-29redhat
redhatnodejs:24-9080020261027142403.rhel92026-10-29redhat
npmbrace-expansion @ 5.0.10 (fixes >= 4.0.0, < 5.0.10)—ghsa
npmbrace-expansion @ 3.0.7 (fixes >= 3.0.0, < 3.0.7)—ghsa
npmbrace-expansion @ 2.1.5 (fixes >= 2.0.0, < 2.1.5)—ghsa
npmbrace-expansion @ 1.1.19 (fixes < 1.1.19)—ghsa

These rows come from Red Hat, Oracle and GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-brace-expansion2.0.1+~1.1.0-1 ... 2.1.7+~1.1.2-1 (8 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.1.7+~1.1.2-1 (6 versions)
  • 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 up to 2.1.7+~1.1.2-1: fixed in 2.1.7+~1.1.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
brace-expansion—
  • 4.0.0 up to 5.0.10: fixed in 5.0.10
  • 3.0.0 up to 3.0.7: fixed in 3.0.7
  • 2.0.0 up to 2.1.5: fixed in 2.1.5
  • every version up to 1.1.19: fixed in 1.1.19
—

Weakness Classification(2)

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

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 115 rows 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 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-102276?
CVE-2026-102276 is a high-severity vulnerability; its CVE record was published on September 28, 2026. The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses…
When was the CVE record for CVE-2026-102276 published?
The CVE record for CVE-2026-102276 was published on September 28, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-102276 actively exploited?
CVE-2026-102276 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102276?
CVE-2026-102276 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102276?
A fix for CVE-2026-102276 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102276 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-102276 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102276

Explore →

Is Your Infrastructure Affected by CVE-2026-102276?

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