CVE-2026-82372 Brocade CVE debrief

Who should care

Defenders responsible for Brocade SANnav systems, particularly those with IPsec policies configured, should assess exposure and prioritize verification and remediation. This includes reviewing current IPsec policies, restricting access to system log files and support bundles, and verifying and upgrading to Brocade SANnav version 3.0.1a or later. Security teams and vulnerability management teams should also be aware of the potential exposure of pre-shared

Why it matters

CVE-2026-82372 requires defenders to verify and remediate Brocade SANnav systems to prevent potential exposure of pre-shared keys and unauthorized access to sensitive data.

• Potential exposure of pre-shared keys used to secure network tunnels
• Increased risk of unauthorized access to sensitive data
• Need for verification of current IPsec policies and system log file access controls
• Priority for upgrading to Brocade SANnav version 3.0.1a or later

Technical summary

Brocade SANnav versions before 3.0.1a improperly handle sensitive data during IPsec policy creation and modification, potentially exposing pre-shared keys to individuals with read access to system log files or support bundles. The vulnerability is caused by the recording of pre-shared keys in application logs during IPsec policy creation and modification. Defenders should prioritize verifying and upgrading to version 3.0.1a or later, reviewing current IPsec policies, and restricting access to system log files and support bundles.

Defensive priority

Defenders should prioritize verifying and upgrading to version 3.0.1a or later, reviewing current IPsec policies, and restricting access to system log files and support bundles.

Recommended defensive actions

• Verify and upgrade to Brocade SANnav version 3.0.1a or later
• Review current IPsec policies and restrict access to system log files and support bundles
• Monitor system logs and support bundles for potential exposure of pre-shared keys
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions and remediation steps is limited. Brocade SANnav versions before 3.0.1a are affected, and defenders should verify and upgrade to version 3.0.1a or later. The CVE record was published on 2026-09-24T20:17:32.353Z and has not been modified since then. There is no evidence of public exploitation, but defenders should review current IPsec policies and restrict access to system log files and support bundles.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.