CVE-2025-12774VulnerabilityPublished 3 Feb 2026

CVE-2025-12774: Brocade SANnav · Cleartext Storage of Sensitive Information

Affects Brocade SANnavSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium · fixed in 3.0 : update Brocade SANnav when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
BrocadeSANnav	Affected =SANnav before 3.0	Fixed in–

AI-suggested

European organizations should implement strict access controls on Brocade SANnav support save files, ensuring only authorized personnel with a legitimate need can access them. Regular audits and monitoring of file access can help detect unauthorized attempts. It is critical to upgrade Brocade SANnav to version 3.0 or later once available, as this version addresses the vulnerability. Until patching is possible, organizations should minimize generation and distribution of support save files and securely delete them after use. Encrypting support save files at rest and in transit can add an additional layer of protection. Additionally, reviewing and hardening privilege management policies to limit high privilege access reduces the risk of exploitation. Organizations should also verify the strength of password encryption mechanisms used by SANnav and consider rotating credentials if exposure is suspected. Finally, integrating this vulnerability into incident response plans will prepare teams to respond promptly if exploitation is detected.

Description

CVE-2025-12774 is a medium severity vulnerability in Brocade SANnav versions before 3.0 involving cleartext storage of sensitive information within the SANnav support save file. The issue arises from a migration script that collects database SQL queries and stores them in the support save file, which can be accessed by an attacker with file access. This exposure could reveal sensitive details such as database table structures and encrypted passwords. Exploitation requires local access to the support save file and high privileges on the system, with no user interaction needed. While no known exploits are currently reported in the wild, the vulnerability poses a risk to confidentiality if the support save file is improperly handled or accessed by unauthorized users. European organizations using Brocade SANnav for storage area network management should be aware of this risk and implement strict access controls and update to version 3.0 or later when available.

Impact

For European organizations, especially those operating large-scale storage area networks using Brocade SANnav, this vulnerability could lead to unauthorized disclosure of sensitive infrastructure information. Exposure of database structures and encrypted passwords could facilitate lateral movement or privilege escalation if attackers combine this information with other vulnerabilities or compromised credentials. Confidentiality breaches could impact compliance with GDPR and other data protection regulations, potentially resulting in legal and financial penalties. Organizations in sectors with critical data storage needs, such as finance, healthcare, and government, may face increased risk due to the sensitivity of their stored data. Although exploitation requires local access with high privileges, insider threats or attackers who have already compromised a system could leverage this vulnerability to deepen their access. The lack of known exploits reduces immediate risk, but the presence of sensitive information in support files remains a persistent security concern.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36848 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Feb 2026, 11:04 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats