# CVE-2026-14443: Incomplete log sanitization during bulk IPsec policy collection in Brocade SANnav before 3.0.1a

> Attackers with log access can obtain IPsec pre-shared keys from Brocade SANnav logs, potentially compromising encrypted network tunnels.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-985r-r2fq-jh5w

## What is CVE-2026-14443?

CVE-2026-14443 is a high-severity vulnerability in Brocade SANnav, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incomplete log sanitization during bulk IPsec policy collection in Brocade SANnav versions before 3.0.1a permit extension switch pre-shared keys to be written to system logs. Individuals with read access to container logs or support archives can obtain these keys, leading to the potential compromise of encrypted network tunnels.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-14443?


## How do I fix CVE-2026-14443?

No fix has been published for CVE-2026-14443 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14443 being exploited?

There is no known exploitation of CVE-2026-14443 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14443 and fix it if it is affected.

What it is: CVE-2026-14443 is a high-severity vulnerability in Brocade SANnav, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14443 in the wild and no public exploit code.

Affected product: Brocade SANnav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14443/ (Markdown: https://insights.sbomify.com/CVE-2026-14443/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14443
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14443
- OSV: https://osv.dev/vulnerability/CVE-2026-14443

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14443/
Summaries are generated and may contain mistakes; the official description above is the record.