External risk intelligence

Broadcom AutoSys Workload Automation Session Credential Falsification Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-126551

Broadcom AutoSys Workload Automation is an enterprise workload orchestration platform. While the Workload Control Center (WCC) provides a web-based interface for management, these systems are typically deployed within internal corporate networks or restricted management segments rather than being exposed directly to the public internet.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in Broadcom AutoSys Workload Automation's Workload Control Center modules that could allow unauthorized session credential falsification. This issue affects specific versions of the software on Windows and Linux systems. The primary concern is to determine if your organization's environment is running the affected software and assess potential exposure.

  • Key flaw: Session credentials can be forged.
  • Why remember: Manages critical automated tasks.
  • Executive takeaway: Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could potentially gain unauthorized session access by exploiting a hard-coded cryptographic key. This vulnerability is present in Broadcom's AutoSys Workload Automation, specifically within the Workload Control Center (WCC) modules on Windows and Linux systems. If an attacker can reach this component, they might be able to forge session credentials, leading to session falsification.

  • No authentication or network access is required.
  • Attackers can falsify session credentials.
  • Risk includes unauthorized session access.

Live Threat

Current exploitation, exposure, and threat context

Session credentials could be falsified, potentially allowing unauthorized access to and manipulation of automated workloads when the Workload Control Center (WCC) is accessible over the network.

  • Workload automation sessions.
  • Network access to WCC.
  • Unauthorized workload control.

Operational Fix

Recommended remediation, mitigation, and detection steps

Determining precise ownership requires an understanding of your specific deployment; however, teams managing enterprise schedulers, application infrastructure, or critical business process platforms likely bear responsibility for Broadcom AutoSys Workload Automation. The first action is to inventory WCC instances, assess their network exposure and business criticality, and identify the accountable system owners before planning remediation.

  • Identify WCC instances and ownership.
  • Verify WCC network reachability and criticality.
  • Plan remediation based on identified risk.

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?

It is an enterprise-grade workload orchestration platform used to schedule, manage, and monitor complex business processes and data jobs. The affected Workload Control Center (WCC) module serves as the primary web-based interface that allows administrators to oversee these automated tasks across distributed Windows and Linux environments.

What does CWE-321 mean for CVE-2026-126551?

CWE-321 refers to the use of a hard-coded cryptographic key. In this vulnerability, the software contains a static, embedded key that is intended to be secret but is easily accessible. This flaw allows an unauthorized person to bypass normal security controls and forge session credentials, effectively masquerading as a legitimate, authenticated user.

How can an attacker trigger this vulnerability?

An attacker exploits this by interacting with the WCC component using the hard-coded key to generate valid session credentials. The vulnerability does not require prior authentication or specialized preconditions; however, it cannot be triggered if the WCC module is completely isolated from all network traffic, as the attacker must be able to reach the service to initiate the forge.

Is my organization at risk for CVE-2026-126551?

If you manage instances of Broadcom AutoSys WCC, you should evaluate your risk. According to Halo Surface Signal, while these modules are often located within internal, restricted management segments, any WCC instance reachable over a network is a potential target. You should prioritize instances with the broadest network reach.

What is the first step to address this CVE?

Begin by conducting an inventory of all WCC instances within your environment to confirm which versions are deployed. Once identified, determine the network accessibility and business criticality of each instance. Finally, coordinate with the system owners to review official vendor guidance for mitigation or update paths.

References