Skip to main content
Menu
CVEs

CVE

Broadcom AutoSys Workload Automation OS command execution in WCC forecast

Affects Broadcom AutoSys Workload Automation WCC 12.1.x through 24.2.00 where the WCC Forecast reporting feature is used. Fixed in 24.2.01 or later.

CVE-2026-126558EUVD-2026-127131

Written by a model from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 24.2.01 or later
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Broadcom AutoSys Workload Automation WCC 12.1.x through 24.2.00 The WCC Forecast reporting feature is used

Published
Last modified
Reference
Last checked
18/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Broadcom AutoSys Workload Automation, including its Workload Control Center (WCC) modules on Windows and Linux, contains an OS command injection flaw caused by incomplete filtering of command delimiters. An attacker with low-privilege login access over the network can run arbitrary operating system commands on the affected host.

Original description

OS Command Injection, Incomplete List of Disallowed Inputs vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows OS Command Injection, Command Delimiters.This issue affects AutoSys Workload Automation: from 12.1 through 24.2.00.

Who should check

Teams running Broadcom AutoSys Workload Automation WCC 12.1.x through 24.2.00 on Windows or Linux, including AE server hosts.

“CVE-2026-126558 - WCC 12.1.x through 24.2.00”

support.broadcom.com

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Broadcom AutoSys Workload Automation WCC 12.1.x through 24.2.00 The WCC Forecast reporting feature is used
  • Upgrade to a fixed version: 24.2.01 or later.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126558 (AutoSys WCC Forecast command injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126558 (entry last updated 2026-11-17):
Affected:
- Broadcom AutoSys Workload Automation: from 12.1, through 24.2.00
Fixed versions: 24.2.01 or later.
Conditions (all must be true for the bug to be hit):
- Broadcom AutoSys Workload Automation WCC 12.1.x through 24.2.00 (source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615)
- The WCC Forecast reporting feature is used (source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126558 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126558 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39615
- https://www.cve.org/CVERecord?id=CVE-2026-126558
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126558
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126558"}.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. First seen by cve.now
  4. Record last updated

Affected versions

  • Broadcom AutoSys Workload Automation

    From 12.1 · through 24.2.00

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126558

Is CVE-2026-126558 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A command injection flaw in the WCC Forecast reporting feature lets an authenticated user run operating-system commands on the AE server host.Source: support.broadcom.com, cve.org

Which versions are affected by CVE-2026-126558?

AutoSys Workload Automation: from 12.1 through 24.2.00.Source: cve.now feed data

Am I affected, and how do I check?

Broadcom lists AutoSys Workload Automation WCC 12.1.x through 24.2.00 as affected, and the issue involves the WCC Forecast reporting feature. To check, compare your WCC version with that range and see whether the WCC Forecast reporting feature is in use.Source: support.broadcom.com, cve.org

How do I fix CVE-2026-126558?

Upgrade to AutoSys Workload Automation 24.2.01 or later.Source: support.broadcom.com, cve.org

More CVEs