External risk intelligence

Broadcom AutoSys WCC Object Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-126553

Broadcom AutoSys Workload Control Center (WCC) is a centralized web-based management interface for workload automation. Such management portals and administrative dashboards are commonly deployed as web applications accessible to users across the network, and while often protected, they frequently possess an externally reachable surface in enterprise environments.

Deserialization

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Broadcom AutoSys Workload Automation's Workload Control Center modules on Windows and Linux could allow for object injection through the deserialization of untrusted data. This issue impacts versions of AutoSys Workload Automation from 12.1 through 24.0.01.

  • Allows attackers to inject malicious code.
  • Affects critical workload automation management.
  • Confirm if AutoSys Workload Automation is in use.

Attack Path

How an attacker could exploit the issue

Attackers can target the Workload Control Center (WCC) of Broadcom AutoSys Workload Automation, a web-based management interface, without needing any prior authentication or access. By exploiting a deserialization vulnerability, an attacker could inject malicious objects into the system, leading to significant compromise.

  • Accessible via the network.
  • Triggers through data deserialization.
  • Allows object injection and full compromise.

Live Threat

Current exploitation, exposure, and threat context

A deserialization of untrusted data vulnerability in Broadcom AutoSys Workload Automation's Workload Control Center (WCC) modules could allow for object injection when supported. This means that an attacker could potentially inject malicious objects into the system, impacting its behavior.

  • System integrity could be affected.
  • Untrusted data could be deserialized.
  • Service behavior may be altered.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Workload Control Center (WCC) is likely managed by application owners and platform teams, with support from network and security teams. The first practical step is to identify all WCC instances, determine their accessibility and business criticality, and then assign ownership for remediation planning based on risk.

  • Application and platform teams own the issue.
  • Verify WCC instances and exposure.
  • Plan risk-based remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Broadcom AutoSys Workload Automation?

Broadcom AutoSys is an enterprise workload automation platform designed to schedule, monitor, and manage complex IT processes across hybrid environments. The Workload Control Center (WCC) module serves as the centralized, web-based management interface for this system, allowing teams to oversee automated workflows, job statuses, and administrative tasks through a unified dashboard.

What is the deserialization vulnerability in CVE-2026-126553?

This CVE involves a weakness classified as CWE-502: Deserialization of Untrusted Data. It occurs when an application takes data received from an external source and recreates an object from it without sufficient validation. In AutoSys WCC, an attacker can supply specially crafted data that the application improperly trusts, allowing them to inject malicious objects and potentially execute unauthorized code or compromise system integrity.

How is this AutoSys vulnerability triggered?

The vulnerability is triggered when the Workload Control Center receives and processes malicious, untrusted data sent over the network. Crucially, successful exploitation does not require the attacker to have a pre-existing account or administrative credentials. The system is only vulnerable if it processes this specific type of malformed data input; standard, legitimate workload monitoring traffic does not trigger the bug.

Is my AutoSys WCC instance at risk?

According to Halo Surface Signal, WCC is a web-based portal frequently deployed with an externally reachable surface, making it accessible across enterprise networks. If your instance is reachable via the network without authentication, it faces a higher profile for potential compromise. You should consider any WCC installation running versions 12.1 through 24.0.01 as a priority for review.

How should I respond to CVE-2026-126553?

Your first step is to inventory all instances of AutoSys Workload Control Center in your environment to confirm if they fall within the affected version range (12.1 to 24.0.01). Once identified, coordinate with your platform and application teams to evaluate the network accessibility of these instances. Prioritize hardening or isolating these systems while you prepare for official vendor-provided remediation steps.

References