Skip to main content

Brocade SANnav CVE-2026-5047

| EUVDEUVD-2026-94756 HIGH
Insecure Storage of Sensitive Information (CWE-922)
2026-10-08 brocade GHSA-vrg4-pprr-h7xv
8.2
CVSS 4.0 · Vendor: brocade
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain access to SANnav logs or supportsave bundle
  2. Exploit
    Locate encoded passwords and auth tokens in files
  3. Execution
    Decode the reversibly-encoded credentials
  4. Impact
    Reuse credentials against SANnav and managed SAN devices

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Secure storage of sensitive data
Exploitation Conditions

Exploitation requires the attacker to obtain SANnav log files or, specifically, the SANnav supportsave diagnostic bundle, which records encoded (reversible, not hashed) passwords and authentication tokens. The description scopes the attacker as 'authenticated ... with access to the log file,' so the gating prerequisite is file-level access to these artifacts rather than an open network request; this is reinforced by the CVSS AV:A (adjacent) and UI:P (passive user interaction, e.g. a supportsave being generated/shared). Limiting factors: affected only in SANnav versions before 2.4.0b and 3.0.0; exploitation depends on the attacker acquiring the log or supportsave output (often exported and handed to support), which is the primary real-world barrier. Note the input vector's PR:N contradicts the description's authenticated-attacker wording - confirm with the vendor.

Impact

The input assigns a CVSS 4.0 base score of 8.2 (High) with vector AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N. The high score is driven by high confidentiality impact (VC:H) plus a subsequent-system confidentiality impact (SC:H), reflecting that the leaked passwords and authentication tokens can be reused against other managed SAN systems. However, there is a direct conflict between the CVSS vector and the description: the vector encodes PR:N (no privileges required), yet the description explicitly states the flaw 'could allow an authenticated attacker with access to the log file' to access the passwords - verify the true privilege requirement with Brocade, as the practical prerequisite appears to be access to log/supportsave files rather than truly unauthenticated network access. The vector's AV:A (adjacent) and UI:P (passive user interaction) further imply the credentials are exposed via artifacts (logs, supportsave diagnostic bundles) rather than a direct remote request. No EPSS score, KEV listing, or public POC is present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: a credible credential-exposure issue (CWE-922, insecure storage) that is genuinely dangerous because passwords are merely 'encoded' (reversible) rather than hashed, but real-world risk is gated by the need to obtain log or supportsave files - making this a patch-soon priority rather than an emergency, and lower in practical urgency than the raw 8.2 suggests.

Exploit ScenarioDerived

An attacker who obtains a SANnav supportsave diagnostic bundle or log files - for example an insider, or someone receiving bundles routinely exported and shared with vendor support - locates the encoded passwords and authentication tokens written to those files and decodes them. The recovered credentials can then be used to authenticate to SANnav and the managed fabric. No public POC is identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Information disclosure in Brocade SANnav before 2.4.0b and 3.0.0 occurs because the product writes encoded passwords and authentication tokens to log files, including the SANnav supportsave diagnostic bundle. An attacker who gains access to those logs or the supportsave output can recover secrets and potentially reuse them, though the description frames this as requiring an authenticated attacker with file-level access and the assessed vector reflects a local/authenticated prerequisite; the input CVSS 4.0 vector lists PR:N, a discrepancy that should be confirmed with the vendor. No public exploit identified at time of analysis, and no CISA KEV confirmation was provided.

RemediationAI

Upgrade to Brocade SANnav 2.4.0b or later for 2.4.x installations, or to 3.0.0 or later for 3.x installations, as specified by the vendor advisory at https://support.broadcom.com/external/content/SecurityAdvisories/0/37933. If immediate patching is not possible, restrict access to SANnav log files and supportsave diagnostic bundles to the minimum necessary personnel, and treat exported supportsave files as sensitive credentials because the stored passwords and tokens are reversibly encoded rather than hashed. Rotate any passwords or authentication tokens that may have been captured in logs or shared diagnostics, review log retention and support-case handling procedures, and monitor for unauthorized access to SANnav log storage. These compensating controls reduce exposure but do not eliminate the underlying weakness, so upgrading remains the primary fix.

Affected VersionsENISA

Brocade SANnav 3.0.0
Brocade SANnav 0 <2.4.0b

Affected Packages

euvd brocade_sannav fix: 2.4.0b

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is classified as CWE-922 (Insecure Storage of Sensitive Information), and the core weakness is that SANnav logs and the supportsave diagnostic bundle record passwords and authentication tokens using reversible encoding rather than one-way hashing. That means anyone who obtains the log file or supportsave archive can decode the values and recover credentials or session tokens. The affected CPE entry is cpe:2.3:a:brocade:brocade_sannav:*:*:*:*:*:*:*:*, which broadly identifies the product, while the advisory scopes the flaw to versions before 2.4.0b and 3.0.0. The input assigns CVSS 4.0 score 8.2 with vector CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N, but the independent assessment uses CVSS 3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, reflecting a local, authenticated/file-access prerequisite rather than an unauthenticated remote condition; this discrepancy should be resolved with the vendor. The disclosure does not directly grant code execution or integrity impact, but it can expose high-value credentials that enable lateral movement or further compromise of the SAN management environment.

Know when Brocade Sannav gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (brocade) PRIMARY 8.2 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Exploitation requires authenticated access to read SANnav log/supportsave files (PR:L, AV:L); leaked credentials enable access to other managed systems (S:C); only confidentiality is affected (C:H, I/A:N).

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (brocade).

CVSS VectorVendor: brocade

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 08, 2026 - 07:01 EUVD
CVE Published
Oct 08, 2026 - 05:18 cve.org
HIGH 8.2

DescriptionCVE.org

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.

Executive ViewAI

Why It Matters

Brocade SANnav, the management platform used to administer SAN fabrics, writes encoded administrative passwords and authentication tokens into its own log files and the supportsave diagnostic bundle, meaning anyone who can read those artifacts can recover credentials that unlock the storage network. Because SANnav credentials typically grant broad control over fabric switches, zones, and attached storage, a single exposed log or a shared support bundle could enable lateral movement into the most sensitive tier of the data center. The vendor has not released a patch, so leadership should treat the exposure as an unmitigated credential-hygiene risk requiring immediate controls on who can access SANnav logs and bundles.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict file-system access to SANnav logs and supportsave bundles to the minimum necessary administrators; stop or sanitize external transmission of diagnostic bundles; rotate all SANnav passwords and authentication tokens that may have been logged; enable encryption and short retention for log archives; and monitor for unauthorized access to log directories. Note that no public exploit identified at time of analysis, but the exposure is a credential-recovery risk once any read access is obtained.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
niche enterprise SAN management software, limited to storage administrators
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2024-3596 CRITICAL
9.0 Jul 09

RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (

CVE-2022-23305 CRITICAL
9.8 Jan 18

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be

CVE-2024-4173 CRITICAL
9.8 Apr 25

A vulnerability in Brocade SANnav exposes Kafka in the wan interface. Rated critical severity (CVSS 9.8), this vulnerabi

CVE-2024-29966 CRITICAL
9.8 Apr 19

Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appl

CVE-2023-31424 CRITICAL
9.8 Aug 31

Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a allows remote unauthenticated users to bypass web

CVE-2022-23302 HIGH
8.8 Jan 18

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write acce

CVE-2024-2240 HIGH
8.6 Feb 14

Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. Rated high severity (CVSS 8.6), this vulnera

CVE-2019-16205 HIGH
8.8 Nov 08

A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID.

CVE-2025-1053 HIGH
8.6 Feb 14

Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obt

CVE-2024-29959 HIGH
8.6 Apr 19

A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the B

CVE-2024-4282 HIGH
8.2 Feb 15

Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. Rated high severity (CVSS 8

CVE-2024-29961 HIGH
8.2 Apr 19

A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. Rated high severity (CVSS 8.2), this vulnerability is

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy