Skip to main content
VulnerabilityPublished

CVE-2026-5047: Brocade SANnav · Insecure Storage of Sensitive Information

Affects Brocade SANnavSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.4.0b soon.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0b
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade Brocade SANnav to 2.4.0b.

Affected software

ProductAffectedFixed in
BrocadeBrocade SANnavAffected
  • <2.4.0b
  • =3.0.0
Fixed in
  • 2.4.0b

AI-suggested

If you cannot patch yet, restrict access to log files containing sensitive information and monitor for unauthorized access. Avoid sharing or distributing supportsave logs without sanitization.

Description

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.

References

Community reviews

Loading reviews…