CVE-2026-14441: Brocade SANnav · Comparison Using Wrong Factors
Affects Brocade SANnavSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.1.0a when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.0a
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 2026.
What to do
Upgrade Brocade SANnav to 3.1.0a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BrocadeSANnav | Affected
| Fixed in
|
AI-suggested
A fix is available as the vendor has updated the internal comparison routines to address the issue. Users should upgrade to Brocade SANnav versions 3.1.0a or later to remediate this vulnerability.
Description
A logic flaw in Java cache key handling object comparison handling could lead to improper identifier resolution when processing specific user account structures. The issue has been remediated by updating the internal comparison routines to ensure accurate object evaluation and prevent potential identity mismatch conditions.