# CVE-2026-14442: Information exposure vulnerability in the job scheduling component of SANnav before 3.0.1a

> Authenticated users can view cleartext credentials in logs, potentially allowing unauthorized access to remote backup targets and protected archives.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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-678q-3q5m-3p8x

## What is CVE-2026-14442?

CVE-2026-14442 is a medium-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

An information exposure vulnerability in the job scheduling component of SANnav allows sensitive credentials to be written to application logs in plain text. When scheduled support save jobs or related operational tasks are executed, sensitive parameters including external server passwords and archive protection keys are logged without proper masking. A local or authenticated user with access to application logs or support bundles can view these cleartext credentials, potentially leading to unauthorized access to remote backup targets or protected archives.

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

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


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

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

## Is CVE-2026-14442 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14442 is a medium-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-14442 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-14442/ (Markdown: https://insights.sbomify.com/CVE-2026-14442/index.md)
```

## Sources

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

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