Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA brocade

CVE-2026-85422: A vulnerability in Brocade ASCG version before 3.5.0 could allow an attacker to obtain a static cryptographic key hardcoded into the…

HighCVSS 8.4 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 33/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Brocade Brocade Active Support Connectivity Gateway 3.5.0.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Brocade Brocade Active Support Connectivity Gateway 3.5.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 8, 2026
Updated
Oct 14, 2026
EPSS
0.1% · 0th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
33 / 40 · 8.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · brocade
8.4
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-85422

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for broadcom records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
broadcombrocade active support connectivity gateway

Versions reported by the vendor

Affected version ranges reported by the assigning authority (brocade). Independent of NVD's CPE analysis and usually ahead of it.

  • Brocade Brocade Active Support Connectivity Gateway

    • before 3.5.0affected · Brocade ASC-G

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • broadcom brocade active support connectivity gatewaybefore 3.5.0

Same product

broadcom: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-87424A vulnerability in the SupportLink API authentication component of Brocade ASCG versions prior to 3.5.0 allows an attacker to bypass…
    34Monitor
  • CVE-2026-85489An authentication flaw exists in the Brocade ASCG administrative management service component.
    34Monitor
  • CVE-2026-85487A path traversal vulnerability exists in the HTTP service component of Brocade ASCG versions before 3.5.0.
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-5649Oct 8, 2026 · An Improper Input Validation vulnerability for the registered case credentials in Brocade ASCG before v3.0 could allow a local…
    27Monitor
  • ← EarlierCVE-2026-85421Oct 8, 2026 · A critical security vulnerability has been identified in Brocade ASCG versions before 3.5.0.
    34Monitor
  • Later →CVE-2026-85423Oct 8, 2026 · A vulnerability has been identified in the data collection service of Brocade ASCG versions before 3.5.0.
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Brocade Brocade Active Support Connectivity Gateway3.5.0Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 12, 2026+36 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-854880 days apartBrocade ASCG before 3.5.0 has a well-known Brocade default password embedded in a script distributed to every customer.
    28Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
X

Weakness class (CWE)

CWE-798 · Use of Hard-coded Credentials

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.

The bug in code

The whole CWE-798 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const SUPPORT_USER = "support";const SUPPORT_PASS = "hardcoded-password";

Fixed

ts
const creds = await provisioning.deviceCredentials(deviceId);if (creds.mustRotate) await forcePasswordChange(deviceId);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Exploit maturity— → none
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records