# CVE-2026-10539: Unauthenticated command injection in Control-M/Server communication command

> Unauthenticated attackers can execute arbitrary commands on Control-M/Server via a communication command, leading to full server compromise.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-qhfm-m6pm-jrq6

## What is CVE-2026-10539?

CVE-2026-10539 is a critical command injection vulnerability in BMC Control-M/Server, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Control-M/Server communication command does not sufficiently filter or sanitize user-supplied input. Under certain conditions, this issue may allow an unauthenticated attacker to execute unauthorized commands on the affected server, potentially leading to compromise of the server. 

This vulnerability affects Control-M/Server versions 9.0.20.x to 9.0.21.200 (included) and potentially earlier unsupported versions.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

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

## Is CVE-2026-10539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10539 is a critical command injection vulnerability in BMC Control-M/Server, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10539 in the wild and no public exploit code.

Affected product: BMC Control-M/Server. 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-10539/ (Markdown: https://insights.sbomify.com/CVE-2026-10539/index.md)
```

## Sources

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

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