# CVE-2025-12679: Plain text pbe key visible in audit log during Brocade SANnav migration from 2.4.0a to 3.0.0

> Authenticated privileged users can view plaintext PBE keys in audit logs during specific migration scenarios, exposing sensitive encryption material.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-33j4-gghf-cv63

## What is CVE-2025-12679?

CVE-2025-12679 is a high-severity vulnerability in Brocade SANnav, published on 2 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in Brocade SANnav before 2.4.0b prints the 
Password-Based Encryption (PBE) key in plaintext in the system audit log
 file. The vulnerability could allow a remote authenticated attacker 
with access to the audit logs to access the pbe key.

Note: The vulnerability is only triggered during a migration and not 
in a new installation. The system audit logs are accessible only to a 
privileged user on the server.

These audit logs are the local server VM’s audit logs and are not 
controlled by SANnav. These logs are only visible to the server admin of
 the host server and are not visible to the SANnav admin or any SANnav 
user.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-12679?

It affects 1 product.


Products: Broadcom Sannav.

## How do I fix CVE-2025-12679?

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

## Is CVE-2025-12679 being exploited?

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

## Other vulnerabilities in Brocade SANnav

- [CVE-2022-2068](https://insights.sbomify.com/CVE-2022-2068/): The c_rehash script allows command injection (critical 9.8)
- [CVE-2022-28163](https://insights.sbomify.com/CVE-2022-28163/): SQL injection in Brocade SANNav (critical 9.8)
- [CVE-2020-15377](https://insights.sbomify.com/CVE-2020-15377/): Server-side request forgery in Brocade SANnav (critical 9.8)
- [CVE-2022-28165](https://insights.sbomify.com/CVE-2022-28165/): Missing authorization in Brocade SANNav (high 8.8)
- [CVE-2025-12772](https://insights.sbomify.com/CVE-2025-12772/): Plaintext Switch admin login password is seen in Brocade SANnav support save (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12679 and fix it if it is affected.

What it is: CVE-2025-12679 is a high-severity vulnerability in Brocade SANnav, published on 2 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12679 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-2025-12679/ (Markdown: https://insights.sbomify.com/CVE-2025-12679/index.md)
```

## Sources

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

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