← Search results
CVE-LINKED INVENTORY34 SECURITY RECORDS
Brocade
Brocade SAnnav
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-2026-5769 | 8 Oct 2026 | Brocade SANnav: < 3.0.1 | Security update provided in Brocade SANnav 3.0.1 | Update reference ↗ |
| CVE-2026-5049 | 8 Oct 2026 | Brocade SANnav: < 3.0.0a | Security update provided in Brocade SANnav 3.0.0a and 3.0.1 | Update reference ↗ |
| CVE-2026-5048 | 8 Oct 2026 | Brocade SANnav: < 3.0.0a | Security update provided in Brocade SANnav 3.0.0a and 3.0.1 | Update reference ↗ |
| CVE-2026-5047 | 8 Oct 2026 | Brocade SANnav: < 2.4.0b, 3.0.0 | Security update provided in Brocade SANnav 2.4.0b, 3.0.0 and 3.0.1 | Update reference ↗ |
| CVE-2024-4282 | 14 Feb 2025 | before 2.3.1b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-10405 | 14 Feb 2025 | Brocade SANnav before 2.3.1b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-2240 | 14 Feb 2025 | Brocade SANnav before 2.3.1b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1053 | 14 Feb 2025 | Brocade SANnav before 2.3.1b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-10404 | 14 Feb 2025 | before 2.3.1b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-2860 | 8 May 2024 | before SANnav v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-2859 | 27 Apr 2024 | v2.3.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-4173 | 25 Apr 2024 | All Versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-4161 | 25 Apr 2024 | before v2.3.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-4159 | 25 Apr 2024 | before v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29969 | 19 Apr 2024 | before v2.3.1, v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-29968 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29967 | 19 Apr 2024 | before Brocade SANnav v2.31 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29966 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29965 | 19 Apr 2024 | before v2.3.1, and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29964 | 19 Apr 2024 | before v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29962 | 19 Apr 2024 | before v2.3.1, and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29963 | 19 Apr 2024 | before v2.3.1, and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29961 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29960 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29959 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29958 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29957 | 19 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29956 | 18 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29955 | 17 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29952 | 17 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29951 | 17 Apr 2024 | before v2.3.1 and v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29950 | 17 Apr 2024 | versions before Brocade SANnav v2.3.1, v2.3.0a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-31925 | 31 Aug 2023 | Brocade SANnav before v2.3.0 and v2.2.2a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-33187 | 9 Dec 2022 | Brocade SANnav versions before v2.2.1 | 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.