Skip to content
CVE-2026-126553: Update AutoSys WCC recovery and deployment baselines

CVE-2026-126553: Update AutoSys WCC recovery and deployment baselines

November 19, 2026

Broadcom’s CNA record rates CVE-2026-126553 Critical, with a CVSS 4.0 score of 9.3. This guide concerns the Workload Control Center (WCC) component of AutoSys Workload Automation.

Separate the version boundaries

Broadcom’s November 17 advisory lists WCC 12.1.x through 24.0.01 as affected. WCC 24.1.00 and later are unaffected because of its platform migration, not a specifically released security fix for this CVE. The vendor recommends 24.2.01 or later for affected customers.

Include retained deployment material

List the WCC versions represented by installation packages, approved machine images and disaster-recovery documentation. Distinguish material retained for historical recovery from material approved for new deployment.

An image catalog entry should identify the WCC version it contains and the person responsible for maintaining it. If the version is unknown, mark the entry unresolved until it can be established from existing build or administrative records. Do not label an image patched solely because its underlying operating system was updated.

Reconcile deployment and recovery records

After a supported WCC upgrade and service restart, record the product version and cumulative level shown in the WCC About dialog. Compare that result with the intended deployment baseline.

Update the recovery runbook so it requires version verification after a restore. Returning to an affected WCC version reopens this remediation item. Keep required historical recovery material under the normal retention policy, with its version limitations visible.

Track outstanding image updates separately from already-updated running installations. This avoids counting a corrected server as proof that future deployments will use the same WCC release.

Acknowledgements

This post was created with assistance from AI.

Last updated on