# CVE-2026-14443: Brocade SANnav incomplete log sanitization in IPsec policy

Source: https://junglewise.ai/threats/cve-2026-14443-incomplete-log-sanitization-during-bulk-ipsec-policy-collection  
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-14443 · Severity: info · Published 2026-09-24

Brocade SANnav, a storage area network management platform, fails to properly sanitize sensitive IPsec pre-shared keys from system logs during bulk policy collection. Attackers with access to container logs or support archives can extract these keys to compromise encrypted network tunnels protecting storage infrastructure.

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-14443 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-14443 being exploited in the wild.

**How severe is CVE-2026-14443?** 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-14443?** A patch was published on 2026-09-22: Fix available 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-14443 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-14443?** 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

Incomplete log sanitization in the SANnav IPsec component (CWE-532) permits pre-shared keys to be written to system logs during bulk IPsec policy collection. An attacker with read access to container logs or support archives can extract these credentials to compromise encrypted tunnels. The vulnerability affects versions before 3.0.1a and is fixed in version 3.0.1a.

## Affected products

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

## Timeline

- 2026-09-22: disclosed
- 2026-09-22: patched: Fix available in version 3.0.1a

## References

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

## Related threats

- [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 sensitive data exposure in IPsec logs](https://junglewise.ai/threats/cve-2026-82372-improper-handling-of-sensitive-data-during-ipsec-policy-creation)
- [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)