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-82372 Overview
CVE-2026-82372 is an information disclosure vulnerability in Brocade SANnav versions before 3.0.1a. The flaw stems from improper handling of sensitive data during IPsec policy creation and modification. Pre-shared keys (PSKs) used to secure network tunnels are written in cleartext to application log files. Any user with read access to system log files or support bundles can retrieve these credentials. The weakness maps to [CWE-532: Insertion of Sensitive Information into Log File].
Critical Impact
Attackers with log read access can recover IPsec pre-shared keys and compromise the confidentiality and integrity of tunnels secured by those keys.
Affected Products
- Brocade SANnav versions prior to 3.0.1a
- IPsec policy configuration workflow within SANnav management
- Support bundles generated from vulnerable SANnav instances
Discovery Timeline
- 2026-09-24 - CVE-2026-82372 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-82372
Vulnerability Analysis
Brocade SANnav manages storage area network fabrics and supports IPsec for securing management-plane traffic. During the creation or modification of an IPsec policy, the application records diagnostic information to its logs. The logging routine does not redact the pre-shared key field before writing the event. As a result, PSK values persist in log files on disk and in any generated support bundles.
The exposure is passive and persistent. Once a key is written to logs, it remains available to anyone who later reads those files, including operations staff, support engineers reviewing bundles, and attackers who gain file-system access. Recovering a PSK enables an adversary on the adjacent network to decrypt captured IPsec traffic or establish an unauthorized tunnel.
Root Cause
The root cause is missing sanitization of sensitive input in the IPsec policy handling code path. The application treats the PSK as ordinary configuration data when generating audit or debug log entries. There is no masking, hashing, or omission applied to secret fields before serialization.
Attack Vector
Exploitation requires low-privileged authenticated access to the SANnav host or to a support bundle derived from it. An insider or a compromised support account can read the log files directly. The attack vector is adjacent network because downstream use of the recovered PSK targets IPsec tunnels on the adjacent management network. No user interaction is required.
No verified public exploit or proof-of-concept code is available. See the Broadcom Security Advisory #38997 for vendor-supplied technical details.
Detection Methods for CVE-2026-82372
Indicators of Compromise
- Presence of IPsec PSK strings in SANnav application log files or rotated archives.
- Support bundles generated before upgrade that contain IPsec policy creation or modification events.
- Unexpected read access to SANnav log directories by non-administrative accounts.
Detection Strategies
- Scan SANnav log files and historical support bundles for IPsec policy events containing key-like strings.
- Audit file-access logs for reads against SANnav log directories by accounts outside the operations team.
- Correlate IPsec tunnel renegotiation or authentication anomalies with prior log-access events.
Monitoring Recommendations
- Enable file integrity monitoring on SANnav log directories and support bundle output paths.
- Alert on creation, download, or external transfer of SANnav support bundles.
- Track administrative changes to IPsec policies and treat each as a trigger to rotate PSKs.
How to Mitigate CVE-2026-82372
Immediate Actions Required
- Upgrade Brocade SANnav to version 3.0.1a or later.
- Rotate all IPsec pre-shared keys configured on affected SANnav instances after upgrade.
- Purge or securely delete pre-upgrade log files and support bundles that may contain PSKs.
- Restrict read access to SANnav log directories to a minimal set of administrators.
Patch Information
Broadcom addresses the issue in Brocade SANnav 3.0.1a. Refer to the Broadcom Security Advisory #38997 for the full fix list and upgrade guidance.
Workarounds
- Limit filesystem access to SANnav log paths through operating system permissions and role separation.
- Avoid generating or sharing support bundles from vulnerable versions; if required, sanitize bundles before transmission.
- Monitor for and immediately rotate any PSK that may have been written to logs prior to patching.
# Configuration example
# Restrict access to SANnav log directories (illustrative)
chown -R sannav:sannav /var/log/sannav
chmod -R 600 /var/log/sannav
# Remove pre-patch support bundles that may contain PSKs
find /var/opt/sannav/support-bundles -type f -name "*.zip" -delete
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

