cve.bz

CVE-2026-126550 AutoSys WCC session identifiers written to log

8.6 high

High (8.6) in broadcom autosys workload automation.

On this page
Insertion of Sensitive Information into Log File, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Reusing Session IDs (Session Replay).This issue affects AutoSys Workload Automation: from 12.1.00 through 24.2.00.

Severity

CVSS 4.0

8.6 high
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-522 Insufficiently Protected Credentials
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A06:2025 Insecure Design, A09:2025 Logging & Alerting Failures
Published
Assigned by
ca (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126550 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126550?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126550?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126550 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • broadcom:autosys workload automation

Versions

From the CNA's record in the CVE List.

ProductAffected
Broadcom AutoSys Workload Automationfrom 12.1.00 through 24.2.00

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).

References

Check your stackJSON