# CVE-2026-82372: Brocade SANnav sensitive data exposure in IPsec logs

Source: https://junglewise.ai/threats/cve-2026-82372-improper-handling-of-sensitive-data-during-ipsec-policy-creation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-24. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

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

Brocade SANnav, a storage area network management platform, improperly logs pre-shared keys used to secure IPsec tunnels when administrators create or modify security policies. Anyone with access to system logs or support bundles can read these credentials and use them to intercept or decrypt network traffic, compromising the security of critical infrastructure communications.

Technologies: [Brocade SANnav](https://junglewise.ai/threats/technologies/sannav), [Brocade SANnav OVA](https://junglewise.ai/threats/technologies/sannav-ova). Vendors: [Brocade](https://junglewise.ai/threats/vendors/brocade).

## Quick answers

**Is CVE-2026-82372 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-82372 being exploited in the wild.

**How severe is CVE-2026-82372?** Informational severity, published 24 September 2026.

**Which products and versions are affected?** Brocade SANnav before 3.0.1a; Brocade SANnav OVA before 3.0.1a.

**Is there a fix for CVE-2026-82372?** A patch was published on 2026-09-22: Fix released 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-82372 attacked?** It is attacked from the adjacent network or with local access, in a network appliance.

**Am I affected by CVE-2026-82372?** Check whether you run Brocade SANnav or Brocade 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

SANnav inserts IPsec pre-shared keys into application logs during policy creation and modification (CWE-532). An attacker with read access to log files or support bundles can extract credentials. The vulnerability affects versions before 3.0.1a; access requires existing system log visibility, and a patch is available in version 3.0.1a and later.

## Affected products

- Brocade SANnav before 3.0.1a
- Brocade SANnav OVA before 3.0.1a

## Timeline

- 2026-09-22: disclosed: Initial publication by Broadcom
- 2026-09-22: patched: Fix released in version 3.0.1a

## References

- [https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38997](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38997)

## Related threats

- [Brocade SANnav incomplete log sanitization in IPsec policy](https://junglewise.ai/threats/cve-2026-14443-incomplete-log-sanitization-during-bulk-ipsec-policy-collection)
- [Brocade SANnav sensitive information exposure in job scheduling logs](https://junglewise.ai/threats/cve-2026-14442-an-information-exposure-vulnerability-in-the-job-scheduling)
- [Brocade SANnav command injection in HTTP service](https://junglewise.ai/threats/cve-2026-82370-unauthenticated-remote-command-injection-in-the-brocade-sannav)
- [Brocade SANnav OS command injection in CLI scripting](https://junglewise.ai/threats/cve-2026-82369-insufficient-input-sanitization-of-shell-metacharacters-in-the)
- [Brocade SANnav access control bypass on internal service ports](https://junglewise.ai/threats/cve-2026-82368-insecure-access-controls-on-internal-service-ports-in-brocade)