Skip to main content
Mallory
HighVulnerability

CVE-2026-10538: Unsafe deserialization in BMC Control-M/Server and Control-M/Enterprise Manager messaging consumer

Published Jul 1, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.9High · v4
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-10538CWE-502 · Deserialization of Untrusted Data

CVE-2026-10538 is a high-severity improper deserialization vulnerability affecting out-of-support BMC Control-M/Server and Control-M/Enterprise Manager versions 9.0.20.x and potentially earlier. The flaw is in messaging consumer functionality that deserializes user-controlled data without sufficiently restricting the set of allowed object types. Because crafted serialized content is accepted and processed on the server side, an authenticated attacker can remotely supply malicious serialized data and cause unintended server-side behavior during deserialization or subsequent object handling.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow an authenticated remote attacker to influence server-side processing by injecting crafted serialized objects into the messaging consumer path. The documented impact is unintended server-side behavior; depending on the reachable gadget types and runtime conditions in the affected deployment, this could include unauthorized application actions, logic manipulation, service instability, or other unsafe execution paths associated with deserialization of attacker-controlled content.

Mitigation

If you can’t patch tonight, do this now.

If immediate remediation is not possible, reduce exposure of the vulnerable messaging consumer functionality by limiting network reachability and restricting access to authenticated interfaces to only trusted administrative or application sources. Minimize attacker access paths, segment affected systems, and monitor for unexpected server behavior or anomalous messaging activity. Because the affected versions are out of support, mitigation should be treated as temporary risk reduction rather than a substitute for upgrading.

Remediation

Patch, then assume compromise.

Upgrade or migrate affected Control-M/Server and Control-M/Enterprise Manager installations from out-of-support 9.0.20.x and potentially earlier releases to a supported vendor release that addresses the issue. Apply all relevant vendor patches and updates. As part of remediation, harden deserialization handling by enforcing strict allowlisting of permitted object types in the messaging consumer functionality and eliminating acceptance of untrusted serialized data where possible.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-10538 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-10538 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-10538?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-10538.
Is there a patch for CVE-2026-10538?
Upgrade or migrate affected Control-M/Server and Control-M/Enterprise Manager installations from out-of-support 9.0.20.x and potentially earlier releases to a supported vendor release that addresses the issue. Apply all relevant vendor patches and updates.
How severe is CVE-2026-10538?
CVE-2026-10538 has a CVSS v4 score of 8.9 (High) and an EPSS score of 0.42% (37th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.