Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable messaging consumer (AV:N) but needs a privileged account (PR:H) and a non-trivial gadget chain (AC:H); deserialization impacts downstream components so S:C with full C/I/A loss.
Primary rating from Vendor (airbus).
CVSS VectorVendor: airbus
Lifecycle Timeline
2DescriptionCVE.org
Messaging consumer functionality allows deserialization of user-controlled data without sufficient restriction of allowed object types in the out of support Control-M/Server and Control-M/Enterprise Manager versions 9.0.20.x and potentially earlier. This issue may allow an authenticated attacker to trigger unintended server-side behavior through crafted serialized content.
AnalysisAI
Server-side object injection in BMC Control-M/Server and Control-M/Enterprise Manager 9.0.20.x (and potentially earlier) lets an authenticated attacker abuse the messaging consumer to deserialize untrusted, type-unrestricted objects, triggering unintended server-side behavior that can escalate to full compromise of the automation server. The affected releases are already out of support, and the CVSS 4.0 base score is 8.9 (High) with high privileges and high attack complexity required. There is no public exploit identified at time of analysis, and the CVE is not listed in CISA KEV.
Technical ContextAI
Control-M is BMC's enterprise workload automation (job scheduling) platform; Control-M/Server orchestrates and executes jobs while Control-M/Enterprise Manager provides the central management console. The flaw is a CWE-502 Deserialization of Untrusted Data weakness: the messaging consumer component accepts serialized objects from a client/message channel and reconstructs them without restricting which object types (classes) may be instantiated. When a deserialization runtime is allowed to build arbitrary gadget-chain objects from attacker-controlled bytes, method side effects during construction/resolution can be chained into unintended logic or code execution. The affected CPEs are cpe:2.3:a:bmc:control-m/enterprise_manager and cpe:2.3:a:bmc:control-m/server, both at 9.0.20.x and earlier.
RemediationAI
Because the impacted 9.0.20.x branch is out of support, the primary remediation is to upgrade Control-M/Server and Control-M/Enterprise Manager to a current, vendor-supported major release that is not affected, following the vendor knowledge article at https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA3cx000000GFKrCAO&type=Solution (no exact fixed 9.0.20.x version was provided in the input, so treat this as an upgrade-off-EOL action rather than an in-branch patch). As compensating controls until upgrade, restrict network reachability of the Control-M messaging/consumer ports so only trusted management hosts can connect (side effect: agents or integrations using those channels must be explicitly allow-listed or they will lose connectivity), tightly limit and monitor the high-privilege accounts that could reach the messaging consumer since exploitation requires PR:H, and enable enhanced logging/alerting on the messaging component to detect anomalous serialized payloads. Do not rely on generic hardening alone; validate any mitigation against BMC's advisory as the out-of-support status means no in-branch security fix should be assumed.
More in Control M Server
View allUnauthenticated command execution in BMC Control-M/Server (versions 9.0.20.x through 9.0.21.200) arises because a Contro
BMC Control-M/Server 9.0.21.300 displays cleartext database credentials in process lists and logs. Rated medium severity
Same weakness CWE-502 – Deserialization of Untrusted Data
View allSame technique Deserialization
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40926
GHSA-w883-5vxm-2pq9