CVE-2026-85422 — Brocade Active Support Connectivity Gateway
HIGHCVE-2026-85422 is a high-severity (CVSS 7.8) Hard-coded Credentials vulnerability in broadcom brocade active support connectivity gateway. A fix is available — see the affected versions and patch details below.
A vulnerability in Brocade ASCG version before 3.5.0 could allow an attacker to obtain a static cryptographic key hardcoded into the software binaries to secure sensitive data at rest…
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-85422.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-85422 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 389,824 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
A vulnerability in Brocade ASCG version before 3.5.0 could allow an attacker to obtain a static cryptographic key hardcoded into the software binaries to secure sensitive data at rest and to protect inter-node communication protocols. An attacker who extracts this key can decrypt stored management credentials or craft forged administrative synchronization messages.
Affected Products
brocade active support connectivity gatewaybroadcomDetection & mitigation playbook
Vendor / applianceDetect
Inventory every broadcom brocade active support connectivity gateway deployment and check each version against the affected-products list above.
Fix
Apply the broadcom brocade active support connectivity gateway security patch or hotfix for CVE-2026-85422 on the affected version, following the vendor advisory for your exact build.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-85422 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.