External risk intelligence

Broadcom AutoSys WCC OS Command Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-126552

Broadcom AutoSys Workload Control Center (WCC) is a centralized web-based management interface used for monitoring and managing enterprise job scheduling. As a web application providing remote administrative control, it is commonly deployed as an accessible service within organizational networks, making it a likely candidate for exposure at the edge or via internal portals.

OS Command Injection

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 critical vulnerability has been identified in Broadcom AutoSys Workload Automation's Workload Control Center modules, impacting systems running on Windows and Linux. This flaw could allow an attacker to execute arbitrary commands on the underlying operating system.

  • Allows unauthorized command execution.
  • Affects workload automation management.
  • Confirm if this system is in use.

Attack Path

How an attacker could exploit the issue

An attacker could gain access to the Workload Control Center, a web interface for managing job schedules, without needing any credentials. By sending specially crafted requests to this interface, an attacker could execute arbitrary operating system commands on the affected servers, potentially leading to a complete compromise of the system.

  • No authentication required for access.
  • Vulnerable component is the Workload Control Center.
  • Risk of operating system command injection.

Live Threat

Current exploitation, exposure, and threat context

A critical vulnerability in Broadcom AutoSys Workload Automation's Workload Control Center could allow an attacker to execute arbitrary operating system commands. This could occur when the system is accessed in a way that bypasses authentication and specifically when the affected modules are present and accessible.

  • System commands could be executed.
  • Remote, unauthenticated access can trigger it.
  • Unauthorized system control is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Critical vulnerability in Broadcom AutoSys Workload Automation's Workload Control Center modules requires immediate attention from teams responsible for application security and infrastructure. Begin by identifying all instances of the affected WCC, assessing their exposure and criticality to business operations, and pinpointing the accountable application or infrastructure owners. Once ownership is confirmed, a risk-based remediation plan, which may involve vendor coordination or patching, should be developed and executed.

  • Application and infrastructure teams own this.
  • Verify WCC exposure and business impact.
  • Plan and coordinate 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 software platform used to automate and manage complex IT job scheduling across large-scale environments. The Workload Control Center (WCC) module serves as the centralized, web-based management interface. IT teams use WCC to monitor job workflows, manage schedules, and perform administrative tasks across their Linux and Windows server infrastructure.

What does OS Command Injection mean for CVE-2026-126552?

This vulnerability involves two weakness classes: Missing Authentication for Critical Function (CWE-306) and OS Command Injection (CWE-78). Essentially, the software fails to verify who is making a request and improperly handles input. This allows an unauthorized user to send malicious data that the server mistakenly interprets as legitimate operating system commands, granting the attacker the ability to run arbitrary instructions on the underlying server.

How is this vulnerability triggered?

The flaw is triggered when an attacker sends a specially crafted request to the WCC web interface. Because the system fails to require authentication, no valid user account or login is needed to initiate the attack. Crucially, the vulnerability relies on the accessibility of the WCC module; if the module is not installed or the service is not running, the specific code path required for this command injection cannot be executed.

Why should I care about CVE-2026-126552?

According to Halo Surface Signal, the Workload Control Center is a web-based interface providing administrative control, making it a high-value target for attackers. Whether deployed at the network edge or within internal portals, any WCC instance reachable over the network is at risk. If your organization relies on this tool for infrastructure management, the lack of required authentication makes unauthorized remote access to your servers a significant concern.

How do I respond to this vulnerability?

Start by identifying every instance of AutoSys WCC running in your environment to determine which servers are affected. Confirm the business criticality of each instance and coordinate with the infrastructure or application owners responsible for those systems. Once you have a clear inventory, prioritize these assets for remediation, which likely involves applying patches or security updates provided by the vendor to close the unauthorized access path.

References