Skip to content
major vulnerability· requires attention

Unauthenticated command injection in Brocade SANnav can alter Fibre Channel fabric configs and container runtimes, risking major storage disruption across enterprises and data centers.

Infrastructure

CVE-2026-82370

8.6
High
EPSS n/aPatch availableSep 26, 2026

Unauthenticated command injection in Brocade SANnav allows admin CLI and container control.

common questions

Is CVE-2026-82370 being exploited?

Not confirmed. CVE-2026-82370 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-82370?

CVE-2026-82370 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-82370?

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

What does CVE-2026-82370 affect?

CVE-2026-82370 affects Brocade SANnav orchestrator < 3.0.1a, Managed Brocade Fibre Channel switches, Containers on SANnav host. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82370?

Upgrade SANnav to 3.0.1a+, restrict management access, audit switch configs.

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

executive summary
technical analysis
affected
Brocade SANnav orchestrator < 3.0.1aManaged Brocade Fibre Channel switchesContainers on SANnav host
impact

Unauthenticated network-adjacent command injection: execute administrative switch CLI commands and control containers; can reconfigure FC fabrics and disrupt storage availability.

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