Broadcom AutoSys Workload Automation auth bypass via hard-coded key in Workload Control Center
Affects AutoSys Workload Automation 12.1 through 24.2.00 where the Workload Control Center (WCC) runs on Windows or Linux. Fixed in 24.2.01.
- Exploited
- No known exploitation
- Fix
- Fixed in 24.2.01
- Who is exposed
- Not reported
Summary
Broadcom AutoSys Workload Automation, specifically its Workload Control Center (WCC) modules on Windows and Linux, contains a hard-coded cryptographic key that lets an attacker forge session credentials. An attacker can exploit this remotely over the network without logging in or any user action, which could give them high levels of access to confidentiality, integrity, and availability.
Written by a model
Original description
Use of Hard-coded Cryptographic Key vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Session Credential Falsification through Forging.This issue affects AutoSys Workload Automation: from 12.1 through 24.2.00.
Who should check
Teams running Broadcom AutoSys Workload Automation WCC 12.1.x through 24.2.00 on Windows or Linux, including the Workload Control Center web tier.
“CVE-2026-126551 - WCC 12.1.x through 24.2.00”
What to do
Upgrade to a fixed version: 24.2.01.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126551 (AutoSys hard-coded key to agent code execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126551 (entry last updated 2026-11-17):
Affected:
- Broadcom AutoSys Workload Automation: from 12.1, through 24.2.00
Fixed versions: 24.2.01.
Conditions (all must be true for the bug to be hit):
- Affects WCC (Workload Control Center) 12.1.x through 24.2.00 on Windows or Linux. (source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126551 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126551 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615
- https://www.cve.org/CVERecord?id=CVE-2026-126551
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126551
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126551"}.Affected versions
- Broadcom AutoSys Workload AutomationFrom 12.1 · through 24.2.00
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- First seen by cve.now
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.45%
- Posted on X by cve.now Nov 17
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
On X 1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | support.broadcom.com · web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126551 |
| Record | NVD · CVE-2026-126551 |
Questions about CVE-2026-126551
Is CVE-2026-126551 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A hard-coded key in AutoSys Workload Automation can let an unauthenticated remote attacker run code on managed System Agent hosts. The advisory describes the impact as remote code execution on those agent hosts.
Source: support.broadcom.com, cve.org
Which versions are affected by CVE-2026-126551?
AutoSys Workload Automation: from 12.1 through 24.2.00.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 12.1 through 24.2.00 of AutoSys Workload Automation are affected when the Workload Control Center (WCC) is in use on Windows or Linux. To check a setup, look at the installed AutoSys version and confirm whether WCC is deployed on the host.
Source: support.broadcom.com, cve.org
How do I fix CVE-2026-126551?
Upgrade to AutoSys Workload Automation 24.2.01 or later, which is the fixed version named in the advisory.
Source: support.broadcom.com, cve.org
Related
- CVE-2026-126553AutoSys WCC unauthenticated deserialization
- CVE-2026-126552AutoSys WCC unauthenticated command execution
- CVE-2026-126558AutoSys WCC Forecast command injection
- CVE-2026-126550AutoSys WCC session identifiers written to log
- CVE-2026-126547AutoSys WCC agent-control authorization bypass
- CVE-2026-126548AutoSys WCC export-feature SSRF
No corrections so far. Something wrong on this page? Report an error.