CVE-2026-87666

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.8% (78th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week
8.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.8%CVSS: 8.6Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Brocade Communications Systems LLC, a Broadcom Company) lists Brocade Fabric OS versions before 9.2.2d and 10.0.0 up to and including 10.0.0a1 as affected. No release containing a fix is confirmed on record.

An OS command injection vulnerability exists in the time and zone management subsystem of Brocade Fabric OS versions before 9.2.2d and 10.0.0 through 10.0.0a1. When updating system timezone settings via the REST API or configuration download routines, the system fails to sanitize input values before processing them in underlying shell execution routines. An authenticated user with low-privilege administrative access can exploit this vulnerability by submitting a crafted timezone string containing shell metacharacters. Successful exploitation allows the attacker to escape the restricted management environment and execute arbitrary shell commands with elevated privileges.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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 (value × EchelonGraph’s weight)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation1.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
1.8%
EPSS %ILE
78th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

October 8, 2026

Last Modified

October 9, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

Support Content Notification - Support Portal - Broadcom support portal

https://support.broadcom.com/external/content/SecurityAdvisories/0/39149

Vendor Advisories for CVE-2026-87666(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 33× 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.

  1. 2026-10-13 05:08 UTCEG score recompute
  2. 2026-10-13 05:07 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  4. 2026-10-12 14:50 UTCEG score recompute
  5. 2026-10-12 03:45 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  6. 2026-10-11 19:16 UTCEG score recompute
  7. 2026-10-11 16:33 UTCEG score recompute
  8. 2026-10-11 15:51 UTCEG score recompute
  9. 2026-10-11 15:51 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  11. 2026-10-11 13:49 UTCEG score recompute
  12. 2026-10-11 03:59 UTCEG score recompute
  13. 2026-10-11 03:58 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  15. 2026-10-10 16:05 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  16. 2026-10-10 04:12 UTCEG score recompute
  17. 2026-10-10 04:12 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  19. 2026-10-09 16:19 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  20. 2026-10-09 04:26 UTCEG score recompute
  21. 2026-10-09 04:26 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  22. 2026-10-09 04:05 UTCEG score recompute
  23. 2026-10-09 04:05 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  24. 2026-10-08 20:17 UTCEG score recompute
  25. 2026-10-08 20:17 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
Show 8 more
  1. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  2. 2026-10-08 14:55 UTCEG score recompute
  3. 2026-10-08 14:55 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  4. 2026-10-08 13:40 UTCEG score recompute
  5. 2026-10-08 13:39 UTCGHSA enrichmentGHSA-4378-8w2h-3mmx · GitHub severity HIGH
  6. 2026-10-08 04:24 UTCEG score recompute
  7. 2026-10-08 04:07 UTCEG score recomputeFirst assessed: 8.6 HIGH
  8. 2026-10-08 04:06 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-87666?
CVE-2026-87666 is a high-severity vulnerability; its CVE record was published on October 8, 2026. An OS command injection vulnerability exists in the time and zone management subsystem of Brocade Fabric OS versions before 9.2.2d and 10.0.0 through 10.0.0a1. When updating system timezone settings via the REST API or configuration download routines, the system fails to sanitize input values…
When was the CVE record for CVE-2026-87666 published?
The CVE record for CVE-2026-87666 was published on October 8, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-87666 actively exploited?
CVE-2026-87666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% probability of exploitation in the next 30 days (78th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87666?
CVE-2026-87666 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87666?
No fix for CVE-2026-87666 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Brocade Communications Systems LLC, a Broadcom Company) lists Brocade Fabric OS versions before 9.2.2d and 10.0.0 up to and including 10.0.0a1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-87666 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87666

Explore →

Is Your Infrastructure Affected by CVE-2026-87666?

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

Book a Demo →Browse All CVEs