Brocade
Fabric OS
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-4661 | 19 Jun 2025 | Brocade Fabric OS 9.1.0 through 9.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-7517 | 21 Nov 2024 | Brocade Fabric OS versions before 9.2.0c, and 9.2.1 through 9.2.1a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-10403 | 21 Nov 2024 | Brocade Fabric OS versions before 8.2.3e2, versions 9.0.0 through 9.2.0c, and 9.2.1 through 9.2.1a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-7516 | 12 Nov 2024 | before 9.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-5460 | 25 Jun 2024 | prior to v9.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29954 | 25 Jun 2024 | before v9.2.1, v9.2.0b, v9.1.1d, and v8.2.3e | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29953 | 25 Jun 2024 | before v9.2.1, v9.2.0b, and v9.1.1d | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-5973 | 5 Apr 2024 | Versions v9.x and before v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-3454 | 4 Apr 2024 | after v9.0 and before v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-4162 | 31 Aug 2023 | Brocade Fabric OS after Brocade Fabric OS v9.0 and before Brocade Fabric OS v9.2.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-3489 | 30 Aug 2023 | Brocade Fabric OS v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31926 | 2 Aug 2023 | before Brocade Fabric OS v9.1.1c and v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31927 | 2 Aug 2023 | before Brocade Fabric OS v9.2.0 and v9.1.1c | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31432 | 1 Aug 2023 | before Brocade Fabric OS v9.1.1c and v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31928 | 1 Aug 2023 | before Brocade Fabric OS v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31428 | 1 Aug 2023 | before Brocade Fabric OS v9.1.1c, v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31431 | 1 Aug 2023 | before Brocade Fabric OS v9.1.1c, v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31427 | 1 Aug 2023 | after 9.1.0 and before Brocade Fabric OS v9.2.0 and v9.1.1c | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31425 | 1 Aug 2023 | after Brocade Fabric OS v9.1.0 and, before Brocade Fabric OS v9.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31429 | 1 Aug 2023 | before Brocade Fabric OS v9.1.1c, v9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.