CVE-2026-82371: Brocade SANnav plaintext exposure of authentication credentials in logs

CVE-2026-82371 · Severity: info · Published 2026-09-24

Brocade SANnav, a storage network management platform, writes administrative switch credentials and session tokens in plaintext to log files. An attacker with access to system logs or support bundles can extract these credentials to gain control of network infrastructure and hijack active management sessions. The vulnerability affects SANnav versions before 3.0.1a and is fixed in version 3.0.1a and later.

Vendors: Broadcom.

Quick answers

Is CVE-2026-82371 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-82371 being exploited in the wild.
How severe is CVE-2026-82371?
Informational severity, published 24 September 2026.
Which products and versions are affected?
Broadcom SANnav before 3.0.1a; Broadcom SANnav OVA before 3.0.1a.
Is there a fix for CVE-2026-82371?
A patch was published on 2026-09-22: Fixed in version 3.0.1a Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82371 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-82371?
Check whether you run Broadcom SANnav or Broadcom SANnav OVA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

CWE-532: Insertion of Sensitive Information into Log Files. The SANnav HTTP entity logs authentication data in plaintext, exposing administrative credentials and active session tokens. Attack requires local or support bundle file access (low privilege); an attacker gains unauthorized access to managed switches and can impersonate active sessions. A security patch is available in version 3.0.1a.

Affected products

  • Broadcom SANnav before 3.0.1a
  • Broadcom SANnav OVA before 3.0.1a

Timeline

  • 2026-09-22: disclosed
  • 2026-09-22: patched: Fixed in version 3.0.1a

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.