# CVE-2026-10538: Improper deserialization handling in Control-M Components

> An authenticated attacker can trigger unintended server-side behavior via crafted serialized data in out-of-support Control-M components.

- **Severity:** High 8.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-w883-5vxm-2pq9

## What is CVE-2026-10538?

CVE-2026-10538 is a high-severity unsafe deserialization vulnerability in BMC Control-M/Enterprise Manager, published on 1 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-10538?


## How do I fix CVE-2026-10538?

No fix has been published for CVE-2026-10538 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10538 being exploited?

There is no known exploitation of CVE-2026-10538 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10538 and fix it if it is affected.

What it is: CVE-2026-10538 is a high-severity unsafe deserialization vulnerability in BMC Control-M/Enterprise Manager, published on 1 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10538 in the wild and no public exploit code.

Affected product: BMC Control-M/Enterprise Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10538/ (Markdown: https://insights.sbomify.com/CVE-2026-10538/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10538
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10538
- OSV: https://osv.dev/vulnerability/CVE-2026-10538

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10538/
Summaries are generated and may contain mistakes; the official description above is the record.