Skip to main content
Mallory
CriticalVulnerability

CVE-2026-10539: Unauthenticated Command Injection in Control-M/Server Communication Command

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.
CVSS9.5Critical · v4
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-10539CWE-77

CVE-2026-10539 is a critical unauthenticated command injection vulnerability in a Control-M/Server communication command. The flaw is caused by insufficient filtering or sanitization of user-supplied input passed to the command-processing path. Under certain conditions, a remote attacker with no authentication may be able to supply crafted input that results in execution of unauthorized commands on the affected Control-M/Server host. The issue affects Control-M/Server versions 9.0.20.x through 9.0.21.200 inclusive, and potentially earlier unsupported versions.

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 remote, unauthenticated execution of unauthorized commands on the affected Control-M/Server, which could lead to compromise of the server. Based on the provided severity metadata, the vulnerability can have high confidentiality, integrity, and availability impact, enabling an attacker to take actions on the server outside intended authorization boundaries.

Mitigation

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

Until patching is completed, restrict network access to Control-M/Server communication interfaces to only trusted hosts and administrative networks, reduce exposure of the vulnerable service, and monitor the server and related logs for suspicious command execution or anomalous activity. Where possible, enforce strict input handling and sanitization controls in surrounding operational workflows, though the primary mitigation is vendor patching.

Remediation

Patch, then assume compromise.

Upgrade Control-M/Server to a fixed version newer than 9.0.21.200 that contains the vendor patch. Because earlier unsupported versions may also be affected, they should be upgraded to a supported fixed release rather than retained in service. Apply the latest vendor update across all affected Control-M/Server instances.

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-10539 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-10539 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-10539?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-10539.
Is there a patch for CVE-2026-10539?
Upgrade Control-M/Server to a fixed version newer than 9.0.21.200 that contains the vendor patch. Because earlier unsupported versions may also be affected, they should be upgraded to a supported fixed release rather than retained in service.
How severe is CVE-2026-10539?
CVE-2026-10539 has a CVSS v4 score of 9.5 (Critical) and an EPSS score of 0.42% (37th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity8Community discussion across Reddit, Mastodon, and other social sources.