# AutoSys hard-coded key to agent code execution

CVE record · `CVE-2026-126551`

- **Identifiers:** `CVE-2026-126551`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** ca
- **Weakness (CWE):** [CWE-321](https://cwe.mitre.org/data/definitions/321.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Technologies:** [Broadcom AutoSys Workload Automation](https://agentprime.io/advisories/technology/broadcom-autosys-workload-automation.md)
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: ca) at 17 Nov 2026, 16:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: Broadcom. Product: AutoSys Workload Automation.
  - affected: `12.1 to 24.2.00, inclusive` (custom)
  - unaffected: `24.2.01 or later`
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Broadcom AutoSys Workload Automation, specifically its Workload Control Center (WCC) modules on Windows and Linux, is affected from 12.1 through 24.2.00. The source describes a hard-coded cryptographic key that lets an attacker forge session credentials, which the description frames as leading to code execution on the agent. The source gives few details about the required network position or privileges. Upgrade to version 24.2.01 or later.

Written 22 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.3 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (ca)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0045, the 39th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 17 Nov 2026, 16:32 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-126551)
- 17 Nov 2026, 16:37 UTC: First seen by agentprime
- 17 Nov 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-126551)

## Sources

- [CVE List: CVE-2026-126551](https://www.cve.org/CVERecord?id=CVE-2026-126551)
- [NVD: CVE-2026-126551](https://nvd.nist.gov/vuln/detail/CVE-2026-126551)

### References from the CNA

- <https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615> (vendor-advisory)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-126551>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-126551/>. Everything for agents: <https://agentprime.io/llms.txt>.
