CVE-2025-55108: BMC Control-M/Agent · Missing Authentication
Affects BMC Control-M/AgentSource CVE Database V5
Not known to be exploited · CVSS 9.5 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BMC Control-M/Agent | Affected
| Fixed in– |
AI-suggested
Organizations should immediately verify their Control-M/Agent configurations to ensure mutual SSL/TLS authentication is enabled between Control-M Server and Agent, as this is the primary mitigation recommended by the vendor. This involves configuring both server and agent components to require and validate client certificates, effectively enforcing strong mutual authentication. Additionally, organizations should upgrade to the latest patched versions once available, or apply any interim security updates or configuration guidance provided by BMC. Network segmentation and firewall rules should restrict access to Control-M/Agent ports to trusted hosts only, minimizing exposure to untrusted networks. Continuous monitoring and logging of Control-M communications can help detect anomalous or unauthorized access attempts. Organizations should also review and harden related infrastructure and credentials to reduce the risk of lateral movement if compromise occurs. Finally, maintaining an incident response plan specific to Control-M environments will help rapidly contain and remediate any exploitation attempts.
Description
The Control-M/Agent is vulnerable to unauthenticated remote code execution, arbitrary file read and write and similar unauthorized actions when mutual SSL/TLS authentication is not enabled (i.e.in the default configuration). NOTE: * The vendor believes that this vulnerability only occurs when documented security best practices are not followed. BMC has always strongly recommended to use security best practices such as configuring SSL/TLS between Control-M Server and Agent. * The vendor notifies that Control-M/Agent is not impacted in Control-M SaaS