Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-14443 Overview
CVE-2026-14443 affects Brocade SANnav versions before 3.0.1a. The flaw stems from incomplete log sanitization during bulk IPsec policy collection. Extension switch pre-shared keys (PSKs) are written to system logs in cleartext. Any user with read access to container logs or support archives can retrieve these keys. Recovered PSKs enable decryption or impersonation of IPsec-protected tunnels between extension switches, compromising storage network confidentiality and integrity. The weakness is tracked as CWE-532: Insertion of Sensitive Information into Log File.
Critical Impact
Local users with log or support-archive access can harvest IPsec PSKs and compromise encrypted SAN extension tunnels.
Affected Products
- Brocade SANnav versions prior to 3.0.1a
- SANnav deployments collecting bulk IPsec policies from extension switches
- Support bundle archives generated by affected SANnav builds
Discovery Timeline
- 2026-09-24 - CVE-2026-14443 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-14443
Vulnerability Analysis
SANnav performs bulk collection of IPsec policy data from managed Brocade extension switches. During this collection routine, the application writes policy payloads to its container log stream. The sanitization logic that should redact secret material is incomplete, so pre-shared keys associated with IPsec security associations are preserved verbatim in the log output.
The exposure is persistent. Logs and support archives retain the PSKs for the lifetime of the retention policy. An operator generating a support bundle for Broadcom escalation inadvertently distributes credential material to anyone handling that bundle.
Root Cause
The root cause is a logging path that lacks field-level redaction for IPsec secret attributes. The bulk collection code serializes the full policy object, including the preSharedKey field, before passing it to the log formatter. Sensitive key material should be masked or omitted at the serialization boundary. This matches the pattern described in CWE-532.
Attack Vector
Exploitation requires local, authenticated access with permission to read SANnav container logs or support archive files. An attacker searches collected log data for IPsec policy entries and extracts the PSK strings. The attacker then uses the keys to establish rogue IPsec tunnels, decrypt captured traffic, or impersonate extension switches participating in replicated SAN traffic. No user interaction is required and attack complexity is low.
No exploit code is publicly available and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. See the Broadcom Security Advisory #38998 for vendor technical details.
Detection Methods for CVE-2026-14443
Indicators of Compromise
- Presence of preSharedKey, psk=, or IPsec policy JSON fragments in SANnav container logs or /var/log archives
- Support bundles exported from SANnav builds earlier than 3.0.1a containing bulk IPsec policy collection output
- Unexpected IPsec tunnel establishment attempts to extension switches from unknown peers
Detection Strategies
- Grep SANnav log archives for IPsec policy keywords and PSK patterns to confirm exposure scope
- Correlate access to SANnav log directories and support archive exports with user identity and privilege level
- Audit distribution lists for prior support bundles sent to vendors or third parties while the vulnerable version was deployed
Monitoring Recommendations
- Alert on reads of SANnav container log paths by non-administrative accounts
- Monitor extension switch IPsec negotiation events for peers outside the approved topology
- Track creation, download, and external transfer of SANnav support archives
How to Mitigate CVE-2026-14443
Immediate Actions Required
- Upgrade SANnav to version 3.0.1a or later as directed in Broadcom Security Advisory #38998
- Rotate all extension switch IPsec pre-shared keys after upgrading
- Purge or securely destroy existing SANnav log files and support archives that contain unredacted PSKs
- Restrict read access to SANnav container logs and support archive directories to a minimal operator group
Patch Information
Broadcom resolved the issue in Brocade SANnav 3.0.1a. The fix completes sanitization of IPsec policy fields written during bulk collection so pre-shared keys no longer appear in log output. Review the vendor advisory for upgrade packages and release notes.
Workarounds
- If upgrade is not immediately possible, disable bulk IPsec policy collection operations in SANnav
- Apply filesystem-level access controls so only privileged administrators can read SANnav log and support archive paths
- Sanitize support bundles manually by removing IPsec policy sections before sharing them outside the organization
# Example: restrict access to SANnav log directories (adapt paths to your deployment)
chown -R sannav:sannav /var/log/sannav
chmod -R 750 /var/log/sannav
# Scrub existing archives for pre-shared key material before distribution
grep -rniE 'preSharedKey|psk=' /var/log/sannav /opt/sannav/support || echo 'no matches'
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

