Skip to content
major vulnerability· requires attention

Enables authenticated attackers to gain full admin control of SAN fabric switches via widely used Brocade SANnav management software; can disrupt enterprise storage and networking.

Networks

CVE-2026-82369

8.6
High
EPSS n/aPatch availableSep 26, 2026

Auth CLI sanitization flaw in Brocade SANnav allows shell escape and full switch admin

common questions

Is CVE-2026-82369 being exploited?

Not confirmed. CVE-2026-82369 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-82369?

CVE-2026-82369 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-82369?

Yes. A fix has been recorded for CVE-2026-82369. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-82369 affect?

CVE-2026-82369 affects Brocade SANnav versions before 3.0.1a, Managed Brocade/Broadcom Fibre Channel fabric switches. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82369?

Upgrade SANnav to 3.0.1a or apply vendor mitigations immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Brocade SANnav versions before 3.0.1aManaged Brocade/Broadcom Fibre Channel fabric switches
impact

Authenticated users with command-exec rights can run arbitrary shell commands on fabric switches, bypass allow-lists and obtain full administrative access.

action required

Immediate action required

affected versions
Brocade SANnav
  • affectedbefore 3.0.1a

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free