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-85490 Overview
CVE-2026-85490 is a path traversal vulnerability in Broadcom Brocade Active Support Connectivity Gateway (ASCG) versions before 3.5.0. The application processes support bundle archives ingested from remote endpoints without sanitizing path traversal sequences in archive entries. An unauthenticated attacker on an adjacent network who can send or intercept ingested archive files can write arbitrary files to restricted locations on the host. This file write primitive can be chained to achieve remote code execution on the underlying system. The flaw is tracked under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Critical Impact
Unauthenticated adjacent-network attackers can write arbitrary files to the ASCG host, enabling potential remote code execution.
Affected Products
- Broadcom Brocade Active Support Connectivity Gateway (ASCG) versions prior to 3.5.0
- Deployments ingesting support bundle archives from remote endpoints
- All ASCG installations exposed to adjacent network traffic from compromised or spoofed endpoints
Discovery Timeline
- 2026-10-08 - CVE-2026-85490 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-85490
Vulnerability Analysis
The vulnerability resides in the archive extraction routine that handles support bundles ingested by ASCG. When the application extracts entries from an incoming archive, it does not validate or normalize relative path components such as ../ within entry names. An attacker who controls or intercepts a support bundle can craft archive entries whose names resolve to directories outside the intended extraction root.
Because the attack path requires only adjacent network reachability and no authentication, any compromised endpoint on a trusted segment can push a weaponized bundle. Successful exploitation writes attacker-controlled files to privileged locations on the ASCG host. Overwriting configuration files, cron jobs, or binaries typically escalates the primitive to remote code execution under the service account.
Root Cause
The root cause is missing input validation in the archive extraction logic. The application concatenates archive entry names with the destination directory without canonicalizing the resulting path or rejecting traversal sequences. This is a canonical instance of CWE-22, commonly referred to as the Zip Slip pattern when it affects compressed archive formats.
Attack Vector
An attacker on an adjacent network either compromises a legitimate endpoint that submits support bundles to ASCG or intercepts and modifies bundles in transit. The attacker embeds archive entries whose filenames contain traversal sequences pointing to sensitive paths. When ASCG ingests and extracts the bundle, the malicious entries land in attacker-chosen locations. Writing to directories such as service start scripts, scheduled task configurations, or web application roots yields code execution. No user interaction and no credentials are required.
No public proof-of-concept exploit is currently available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2026-85490
Indicators of Compromise
- Unexpected files written outside the ASCG support bundle extraction directory, particularly in system binary or configuration paths
- Support bundle ingestion events originating from endpoints that do not normally submit bundles
- Archive entries containing ../ sequences or absolute paths observed in ASCG application logs
- New or modified cron jobs, systemd units, or startup scripts on the ASCG host following bundle ingestion
Detection Strategies
- Inspect ASCG application and extraction logs for archive entries with traversal patterns or non-canonical paths
- Monitor filesystem integrity on the ASCG host, flagging writes outside expected extraction directories
- Alert on process executions spawned by the ASCG service account that fall outside its normal binary set
Monitoring Recommendations
- Enable verbose logging on the ASCG support bundle ingestion pipeline and forward events to a central SIEM
- Baseline normal bundle submission sources and alert on new or anomalous submitters on the adjacent network
- Monitor outbound connections from the ASCG host that could indicate post-exploitation command-and-control activity
How to Mitigate CVE-2026-85490
Immediate Actions Required
- Upgrade Broadcom Brocade ASCG to version 3.5.0 or later as published in the vendor advisory
- Restrict network reachability to the ASCG management and ingestion interfaces to trusted administrative segments only
- Audit recent support bundle ingestion events and inspect the ASCG host filesystem for unauthorized file writes
- Rotate credentials and keys stored on the ASCG host if compromise is suspected
Patch Information
Broadcom has addressed CVE-2026-85490 in ASCG version 3.5.0. Refer to the Broadcom Security Advisory #38389 for official patch details, affected build numbers, and upgrade guidance.
Workarounds
- Place the ASCG ingestion interface behind a firewall or ACL restricting access to known, authenticated endpoints
- Disable or quarantine support bundle ingestion from endpoints that cannot be upgraded or hardened
- Apply host-based integrity monitoring to detect unauthorized writes outside the designated extraction directory until the patch is deployed
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

