CVE-2026-10538
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMessaging 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe vulnerability exists in the messaging consumer functionality of Control-M/Server and Control-M/Enterprise Manager (versions 9.0.20.x and earlier). The application deserializes user-controlled data without restricting which object types can be instantiated, allowing an authenticated attacker to send crafted serialized payloads that could execute arbitrary code or cause unintended server-side behavior.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Control-M versionCheck installed Control-M/Server or Control-M/Enterprise Manager version using version lookup commands, configuration files, or the Control-M version display utilityAffected if version is 9.0.20.x or earlier
-
Identify messaging consumer configurationInspect Control-M messaging configuration files and service definitions to locate active consumer endpoints and deserialization handlersAffected if messaging consumer functionality is enabled and configured to process incoming serialized data
-
Confirm authentication enforcement on messaging interfacesReview access control settings, authentication configuration, and user permissions for Control-M messaging servicesAffected if messaging interfaces permit authenticated attacker access or have weak authentication controls
-
Check for serialization allowlist controlsInspect JVM system properties, security policy files, or application-level serialization restrictions for configured allowlists or blocklistsAffected if no serialization allowlist controls are implemented and arbitrary object types can be deserialized
-
Assess network exposure of messaging servicesIdentify listening ports and network bindings for Control-M messaging services, review firewall rules and network segmentationAffected if messaging interfaces are accessible from untrusted networks without network-level restrictions
A user is affected if running Control-M version 9.0.20.x or earlier with messaging consumer functionality enabled and accessible to an authenticated attacker without serialization allowlist protections in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedSince affected versions are out of support, upgrade to a currently supported Control-M release. If immediate upgrade is not feasible, restrict network access to messaging interfaces and implement serialization allowlist controls at the application or JVM level.
Latest supported Control-M version (contact BMC for current supported releases)
- Contact BMC Control-M support to obtain information on currently supported versions
- Upgrade Control-M/Server and Control-M/Enterprise Manager to the latest supported version as recommended by BMC
- Verify the upgrade resolves the deserialization vulnerability by reviewing release notes or consulting BMC support
- Ensure authentication mechanisms are properly configured to limit exposure to authenticated attackers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10538 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10538 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data