Cross-fabric access via unchecked fabric identifier
Published Oct 8, 2026 · Updated Oct 8, 2026
Authorization bypass in Brocade Fabric OS before 9.2.2d and 10.0.0 through 10.0.0a1 lets remote authenticated users access other Virtual Fabrics. The Fabric OS CLI accepts a crafted request containing an arbitrary fabric identifier without enforcing the user's Virtual Fabric authorization boundary. A restricted account in one Virtual Fabric is required; it can perform unauthorized cross-fabric operations and read other tenants' configuration details.
Summary
What happened
Authorization bypass in Brocade Fabric OS before 9.2.2d and 10.0.0 through 10.0.0a1 lets remote authenticated users access other Virtual Fabrics. The Fabric OS CLI accepts a crafted request containing an arbitrary fabric identifier without enforcing the user's Virtual Fabric authorization boundary. A restricted account in one Virtual Fabric is required; it can perform unauthorized cross-fabric operations and read other tenants' configuration details.
The record
- CVE
- CVE-2026-87687
- Published
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Vendor
- Brocade Communications Systems
- Product
- Fabric OS
- Classifications
- CWE-88
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 8, 2026CVE publishedPublication date reported by the CVE source.
- Oct 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.2.2d
- Affected versionversion=10.0.0 <=10.0.0a1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started