CVE-2026-87687 is a high severity cross-fabric access flaw in Brocade Fabric OS, scored 7.3. Boundaries imply 9.2.2d or later, or a release after 10.0.0a1. 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 9.2.2d.
- Brocade Fabric OS 10.0.0 through 10.0.0a1.
Severity in the record: High (7.3), vector CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Weakness: CWE-88.
Fix: Boundaries imply 9.2.2d or later, or a release after 10.0.0a1. 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.
- Check whether Virtual Fabrics are in use. The scenario depends on users restricted to one Virtual Fabric.
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 per-fabric role assignments and look for unexpected cross-fabric activity in switch logs.
- Record the change, then recheck the version to confirm it took effect.
Why it matters
A restricted user in one Virtual Fabric can submit a request carrying an arbitrary fabric identifier and operate on, or view configuration of, fabrics they were never granted. The record tags this CWE-88, argument injection, and describes it as an authorization and input validation flaw. This matters most where Virtual Fabrics separate tenants or business units.
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
Who is at risk most?
Organizations that use Virtual Fabrics to separate tenants or teams, since a restricted user could reach other fabrics.
Sources
-
Broadcom advisory: 39081
-
Safeguard Gold: CVE-2026-87687
Last reviewed: 18 October 2026.
