Quick answers
- Is CVE-2026-82369 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82369 being exploited in the wild.
- How severe is CVE-2026-82369?
- Informational severity, published 23 September 2026.
- Which products and versions are affected?
- Brocade SANnav before 3.0.1a; Brocade SANnav OVA before 3.0.1a.
- Is there a fix for CVE-2026-82369?
- A patch was published on 2026-09-22: Brocade SANnav 3.0.1a Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82369 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-82369?
- Check whether you run Brocade SANnav or Brocade SANnav OVA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An OS command injection vulnerability (CWE-78) exists in the SANnav SSH CLI scripting component where shell metacharacters are not properly sanitized. An authenticated attacker with command execution permissions can break out of restricted execution contexts to run unauthorized shell commands across target fabric switches, bypassing command allow-lists and obtaining full administrative access.
Affected products
- Brocade SANnav before 3.0.1a
- Brocade SANnav OVA before 3.0.1a
Timeline
- 2026-09-22: disclosed
- 2026-09-22: patched: Brocade SANnav 3.0.1a