CVE-2026-87682 is a high severity command injection flaw in Brocade Fabric OS, scored 8.8. 10.0.1 is the boundary in the record. Check your installed version against the affected list below, then patch or restrict access until you can. The record does not flag it as exploited.
What's affected
- Brocade Fabric OS before 10.0.1.
Severity in the record: High (8.8), vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Weakness: CWE-78.
Fix: 10.0.1 is the boundary in the record. Confirm in the advisory. The record gives the affected range only. The exact fixed builds are listed in the Broadcom advisory, which you should read before scheduling the upgrade.
How to check if you're exposed
- Fabric OS exposes its running version from the switch command line. The
firmwareshowcommand is the usual way to read it; confirm the command and output format against your Fabric OS release documentation. - Repeat on every switch, director and extension blade, since versions can differ across a fabric.
- Compare each version with the affected range above and with the fixed builds named in the Broadcom advisory.
- If you use directory-based (for example LDAP or RADIUS) accounts for switch login, note them in your exposure review.
Run these on every affected device, including ones in remote sites, labs and spares that are powered on.
What to do now
- Confirm the version of every affected system using the checks above.
- Read the vendor advisory linked in Sources and note the fixed version for your release line.
- Schedule the update, starting with systems that face untrusted networks or hold the most sensitive data.
- In the meantime: review the security of the directory service used for switch authentication.
- Record the change, then recheck the version to confirm it took effect.
Why it matters
Several input handling flaws in remote connection validation and session verification for directory-based accounts let untrusted input with shell metacharacters reach internal execution wrappers. This is CWE-78. The record notes that either an authenticated user or a compromised directory service account could exploit it, so your directory server becomes part of the attack surface for these switches.
The record's KEV flag is false, so this post makes no claim that the flaw is exploited in the wild. That can change, so recheck the CISA catalog from time to time.
Network and management devices are patched less often than servers, because upgrades mean planned downtime. That gap is where a flaw like this stays open longest, so build the version check into your regular inventory.
The vector string in the record is a compact summary of how the flaw is reached and what it costs. AV is the attack vector (network, adjacent or local), PR is the privilege the attacker needs, and the C, I and A letters give the impact on confidentiality, integrity and availability. Read it against your own network layout rather than relying on the score alone.
After you patch
Patching is not the end of the job. Recheck the version on each system, because an upgrade that failed or rolled back looks the same as a success until someone looks. Keep the advisory link with your change record so the next reviewer can see why the update happened.
If you cannot patch soon, write down the reason, the compensating control you chose and a date to revisit. Exceptions without a date tend to become permanent.
Quick check
Why does the directory service matter?
The record says a compromised directory service account can exploit the flaw, so a breach there can reach the switch.
Sources
-
Broadcom advisory: 39076
-
Safeguard Gold: CVE-2026-87682
Last reviewed: 18 October 2026.
