Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-5049 Overview
CVE-2026-5049 is a path traversal vulnerability [CWE-22] in the Zone Alias Import flow of Broadcom Brocade SANnav management software. A local authenticated attacker on an adjacent network can write uploaded content outside the intended directory. The flaw allows arbitrary file writes to locations controlled by the attacker, which can corrupt application state or overwrite sensitive files on the SANnav host.
The issue affects all Brocade SANnav releases prior to version 3.0.0a. Broadcom addressed the vulnerability in SANnav 3.0.0a.
Critical Impact
An authenticated adjacent-network attacker can write files outside the Zone Alias Import directory on the SANnav management server, enabling tampering with application files on the Storage Area Network (SAN) management host.
Affected Products
- Broadcom Brocade SANnav versions earlier than 3.0.0a
- Deployments using the Zone Alias Import feature
- SAN management hosts running vulnerable SANnav builds
Discovery Timeline
- 2026-10-08 - CVE-2026-5049 published to the National Vulnerability Database (NVD)
- 2026-10-14 - Last updated in NVD
Technical Details for CVE-2026-5049
Vulnerability Analysis
Brocade SANnav is Broadcom's management application for Fibre Channel SAN fabrics. The Zone Alias Import flow accepts an uploaded file that contains zone alias definitions and stores the content on the SANnav server for processing.
The import handler fails to validate or canonicalize file path components supplied with the upload. An authenticated user can craft an upload whose target path contains traversal sequences such as ../, causing the server to write the uploaded content to a location outside the intended import directory.
Because the write occurs with the privileges of the SANnav service, the attacker can place or overwrite files anywhere the service account can reach. This creates a path from a low-privilege authenticated session to tampering with application binaries, configuration files, or scheduled tasks on the management host.
Root Cause
The root cause is insufficient input sanitization on the filename or path parameter processed by the Zone Alias Import routine. The code does not reject traversal sequences and does not confine the final write target to the intended base directory, matching the pattern described by CWE-22: Improper Limitation of a Pathname to a Restricted Directory.
Attack Vector
Exploitation requires an authenticated account on SANnav and adjacent network access to the management interface. The attacker uploads a file through the Zone Alias Import workflow with a crafted path that escapes the import directory. No user interaction is required beyond the attacker's own session, and no elevated privileges are needed prior to the write.
No public proof-of-concept exploit is available at this time, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Detection Methods for CVE-2026-5049
Indicators of Compromise
- Files written under the SANnav installation tree with modification timestamps that do not match a patching or upgrade event
- Zone Alias Import audit entries referencing filenames containing .., /, or \ sequences
- Unexpected files appearing in system directories writable by the SANnav service account
- New or altered SANnav configuration, script, or JAR files on the management host
Detection Strategies
- Review SANnav application and web server logs for POST requests to the Zone Alias Import endpoint with suspicious filename parameters
- Enable file integrity monitoring on the SANnav install directory and adjacent system paths to flag writes originating from the SANnav service process
- Correlate authenticated SANnav user sessions with file write events on the host operating system
Monitoring Recommendations
- Forward SANnav audit logs and host filesystem telemetry to a central Security Information and Event Management (SIEM) platform for retention and correlation
- Alert on any Zone Alias Import activity performed by accounts that do not routinely manage zoning
- Monitor SANnav user account creation and role changes that could precede an attempted upload abuse
How to Mitigate CVE-2026-5049
Immediate Actions Required
- Upgrade Brocade SANnav to version 3.0.0a or later on all management servers
- Restrict network access to the SANnav management interface to trusted administrative subnets only
- Audit SANnav user accounts and remove or disable any that do not require active access
- Review recent Zone Alias Import activity for signs of attempted path traversal
Patch Information
Broadcom has released a fixed build in Brocade SANnav 3.0.0a. Refer to the Broadcom Security Advisory #37931 for the authoritative advisory, affected versions, and upgrade guidance.
Workarounds
- Limit use of the Zone Alias Import feature to a small set of trusted administrators until patching is complete
- Enforce network segmentation so only authorized management hosts can reach the SANnav web interface
- Apply least privilege to SANnav user roles and avoid granting zoning import permissions to general operators
- Enable detailed audit logging on SANnav and the underlying host to support forensic review if exploitation is suspected
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

