CVE-2026-126553

waiting for further signalsZero needs more public information before it can validate it.

GHSA-6x63-6qfc-frph ↗EUVD-2026-127127 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Broadcom AutoSys Workload Automation >= 12.1, <= 24.0.01
CWE-502 Deserialization of Untrusted Data
ETK-2026-4692Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 02h 48msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h34m
0
+4h
+6h
+8h
+10h
+12h

description

AutoSys Workload Automation Workload Control Center modules on Windows and Linux are affected from version 12.1 through 24.0.01. An attacker may trigger object injection through unsafe deserialization; the advisory does not specify the required access or attack path.

mitigation

Restrict network access to Workload Control Center modules to trusted administrative users and systems while monitoring for vendor remediation. No fixed version is recorded in the advisory.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-17 16:44Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-17 16:44Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-126553

{
  "etk_id": "ETK-2026-4692",
  "cve_id": "CVE-2026-126553",
  "display_id": "CVE-2026-126553",
  "ghsa_id": "GHSA-6x63-6qfc-frph",
  "euvd_id": "EUVD-2026-127127",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unsafe deserialization in AutoSys Workload Control Center",
  "summary": "AutoSys Workload Automation Workload Control Center modules on Windows and Linux are affected from version 12.1 through 24.0.01. An attacker may trigger object injection through unsafe deserialization; the advisory does not specify the required access or attack path.",
  "mitigation": "Restrict network access to Workload Control Center modules to trusted administrative users and systems while monitoring for vendor remediation. No fixed version is recorded in the advisory.",
  "vendor": "Broadcom",
  "product": "AutoSys Workload Automation",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1, <= 24.0.01"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "AutoSys Workload Automation",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.810932666666666,
  "t0_at": "2026-11-17T16:44:14.717000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T16:44:14.717000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-17T16:44:14.717000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126553"
    }
  }
}

published 2026-11-17 17:26Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.