Skip to main content
VulnerabilityPublished

CVE-2026-85490: Brocade Active Support Connectivity Gateway · Path Traversal

Affects Brocade Active Support Connectivity GatewaySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 3.5.0 soon.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.5.0
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade Brocade Active Support Connectivity Gateway to 3.5.0.

Affected software

ProductAffectedFixed in
BrocadeBrocade Active Support Connectivity GatewayAffected
  • <3.5.0
Fixed in
  • 3.5.0

AI-suggested

A fix is available in Brocade Active Support Connectivity Gateway version 3.5.0 and later. Users should upgrade to version 3.5.0 or above to remediate this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes. Patch status is confirmed by the version boundary in the affectedVersions field.

Description

When Brocade ASCG before 3.5.0 processes support bundle archives ingested from remote compromised endpoints, the application fails to sanitize path traversal sequences contained within archive entries prior to extraction. An unauthenticated remote attacker capable of sending or intercepting ingested archive files can leverage this flaw to write arbitrary files to restricted locations on the underlying host, potentially leading to remote code execution.

References

Community reviews

Loading reviews…