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