Skip to main content

Brocade SANnav CVE-2026-85417

| EUVDEUVD-2026-86485 MEDIUM
Insertion of Sensitive Information into Log File (CWE-532)
2026-09-25 brocade GHSA-m4mj-q4v8-3j57
6.4
CVSS 4.0 · Vendor: brocade
View

Attack ChainAIDerived

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

  1. Access
    Obtain read access to SANnav logs or support bundle
  2. Delivery
    Locate unmasked SNMP auth/privacy passwords in log entries
  3. Exploit
    Extract cleartext SNMP credentials
  4. Execution
    Authenticate to monitored switches with SNMP
  5. Impact
    Gain read/management access to switch fabric

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
Exploitation Conditions

Exploitation requires (1) the specific configuration conditions under which SANnav's logging subsystem fails to mask SNMP authentication and privacy passwords, and (2) an actor with read access to SANnav application logs or the generated support bundles. Per the CVSS PR:L, the attacker must already hold some privilege (log/support-bundle read); it is not remote-unauthenticated. Limiting factors: credentials only appear 'under specific configuration conditions' (non-universal), the disclosed SNMP credentials must correspond to reachable monitored switches for the downstream management access to matter, and the primary risk is realized by insiders or a post-compromise actor rather than an external attacker.

Impact

This is a genuine but bounded issue best characterized as a credential-hygiene/information-disclosure flaw rather than a directly remotely exploitable one. The vendor CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) with high subsequent-system impact (SC:H/SI:H/SA:H) yields only 6.4 (Medium), driven mostly by the CHAINED compromise of monitored switches rather than direct impact on SANnav itself. Note a discrepancy worth verifying with the vendor: the description implies exploitation requires read access to system logs or support bundles - which is inherently a local/file-read prerequisite - yet the vendor scored AV:A (adjacent network); AV:L is more consistent with the described access model. There is no EPSS score, no CISA KEV listing, and no public exploit code identified at time of analysis, so this is not evidence of widespread or automatable exploitation; realistic risk is that of an insider or a post-compromise attacker with log/bundle access harvesting SNMP credentials. This should be treated as a medium-priority patch/config-review item, not an emergency - the high subsequent-system numbers reflect what stolen SNMP credentials could enable downstream, not the ease of the initial disclosure.

Exploit ScenarioDerived

An operator, support engineer, or low-privileged user who can read SANnav application logs or generate/access a support bundle opens the logs and finds SNMP v3 authentication and privacy passwords recorded in cleartext due to incomplete masking under certain configurations. They reuse those credentials to gain read or management access to the fabric switches SANnav monitors. No public exploit code exists; the 'exploit' is simply reading a log file.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 25, 2026

Incomplete property masking in Brocade SANnav's logging subsystem can cause SNMP authentication and privacy passwords to be written into application logs whenever specific configuration conditions are met, so anyone who can read those logs or a generated support bundle can recover the credentials and use them for unauthorized read or management access to the monitored switch environment. The flaw is not remotely exploitable by an unauthenticated attacker: per the available CVSS data (PR:L) and our independent assessment (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), exploitation requires an actor who already holds log or support-bundle read privileges, and the sensitive values only appear under non-universal configuration conditions. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical risk is a credential-hygiene and information-disclosure exposure realized by insiders or by a post-compromise actor who reuses the recovered SNMP credentials against reachable switches.

RemediationAI

No vendor-released patch identified at time of analysis, so remediation must start with the vendor advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39001 to check for an updated SANnav build and apply it as soon as it is published. Until then, treat every SNMP authentication and privacy password that may have transited SANnav logging as compromised: rotate SNMPv3 credentials on all monitored switches, and re-key them on the SANnav side, accepting the operational cost of a fabric-wide credential change window. Restrict read access to the SANnav log directories and support-bundle output to the minimum set of administrators (filesystem ACLs and role-based access in SANnav), since the flaw is only exploitable by an actor who can already read those artifacts, and scrub or securely delete support bundles after use rather than leaving them on shared storage. Where possible, reduce log verbosity or disable the diagnostic/debug logging profile that captures SNMP configuration properties, understanding that this may hamper troubleshooting and could hide the very events needed to detect exploitation. Additionally, monitor SANnav logs for credential material and audit switch-side SNMP access from unexpected sources as a detective control, since no public exploit code was identified at time of analysis and exploitation would most likely appear as anomalous legitimate-looking SNMP sessions.

Affected VersionsENISA

SANnav before 3.0.1a

Affected Packages

euvd sannav_before no fix

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-532 (Insertion of Sensitive Information into Log File) and sits in SANnav's logging/masking layer rather than in an authentication or network protocol handler. SANnav Management Portal and its related components manage Brocade SAN switches and use SNMP - typically SNMPv3 USM, where the 'authentication password' protects message integrity/authenticity and the 'privacy password' drives payload encryption - to discover, monitor and configure those switches. The vendor's logging subsystem is supposed to redact these secrets as part of property masking before serializing configuration and diagnostic events, but the masking is incomplete under certain configuration conditions, so the plaintext credential values end up in log files and in support bundles collected for troubleshooting. Because the leaked secrets are reusable credentials for downstream devices, the vendor's CVSS 4.0 vector scores the impact as scope-changed (SC:H/SI:H/SA:H) even though direct confidentiality impact on SANnav itself is rated low (VC:L). Our independent assessment is more conservative about reachability, treating it as a local, low-privilege confidentiality-only issue (S:U/C:H/I:N/A:N) rather than a broadly exploitable remote flaw. The CPE cpe:2.3:a:brocade:sannav:*:*:*:*:*:*:*:* is version-agnostic, indicating the advisory does not pin the defect to a single build.

Know when 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 6.4 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H
vuln.today AI 5.5 MEDIUM

Reading logs/support bundles is a local, low-privilege action (AV:L/PR:L); direct impact is disclosure of SNMP credentials (C:H), with switch compromise being a separate chained consequence, so I:N/A:N.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/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:N/SI:N/SA:N

Primary rating from Vendor (brocade).

CVSS VectorVendor: brocade

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

DescriptionCVE.org

Incomplete property masking in the SANnav logging subsystem permits SNMP authentication and privacy passwords to be recorded in application logs under specific configuration conditions. Individuals with read access to system logs or support bundles can retrieve these credentials, leading to unauthorized read or management access to monitored switch environments

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
niche enterprise SAN fabric management appliance software, storage-industry specific
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

More in Sannav

View all
CVE-2022-2068 HIGH
7.3 Jun 21

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas

CVE-2026-14443 HIGH POC
8.4 Sep 24

Incomplete log sanitization in Brocade SANnav before 3.0.1a causes extension switch IPsec pre-shared keys (PSKs) to be w

CVE-2022-28163 CRITICAL
9.8 May 06

In Brocade SANnav before Brocade SANnav 2.2.0, multiple endpoints associated with Zone management are susceptible to SQL

CVE-2022-28165 HIGH
8.8 May 06

A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an

CVE-2026-82368 HIGH
8.7 Sep 23

Brocade SANnav deployments running versions before 3.0.1a expose backend management service ports without adequate acces

CVE-2026-82369 HIGH
8.6 Sep 23

Command injection in the Brocade SANnav CLI scripting component lets an authenticated user who already holds command-exe

CVE-2026-82372 HIGH
8.5 Sep 24

Pre-shared keys used for IPsec tunnel configuration are recorded in cleartext inside application log files by Brocade SA

CVE-2026-82371 HIGH
8.5 Sep 24

Plaintext disclosure of administrative switch credentials and live session tokens in Brocade SANnav discovery-service lo

CVE-2025-12774 HIGH
7.5 Feb 03

A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries

CVE-2022-28168 HIGH
7.5 Jun 27

In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored usin

CVE-2022-28166 HIGH
7.5 Jun 27

In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Sup

CVE-2026-14442 MEDIUM
6.9 Sep 24

Cleartext credential exposure in the job scheduling component of Brocade SANnav causes external server passwords and arc

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