CVE-2025-55114: BMC Control-M/Agent · Incorrect Behavior Order
Affects BMC Control-M/AgentSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BMC Control-M/Agent | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Immediately inventory and identify all Control-M/Agent instances running affected versions (9.0.18, 9.0.19, 9.0.20). 2) Monitor BMC communications for official patches or updates addressing CVE-2025-55114 and apply them promptly once available. 3) As a temporary workaround, restrict network access to Control-M/Agent endpoints by implementing strict firewall rules or network segmentation to allow only trusted Control-M/Server IP addresses, minimizing exposure to unauthorized connections. 4) Enable and review detailed logging on Control-M/Agent to detect unusual SSL/TLS handshake attempts or resource usage spikes that may indicate exploitation attempts. 5) Conduct regular vulnerability scans and penetration tests focusing on SSL/TLS configurations and Control-M/Agent endpoints to identify potential weaknesses. 6) Coordinate with network security teams to monitor for anomalous traffic patterns that could signal exploitation attempts. 7) Educate operational teams about the vulnerability and ensure incident response plans include scenarios involving Control-M/Agent disruptions. These steps go beyond generic advice by focusing on network-level controls, monitoring, and operational preparedness tailored to the specific vulnerability characteristics.
Description
The improper order of AUTHORIZED_CTM_IP validation in the Control-M/Agent, where the Control-M/Server IP address is validated only after the SSL/TLS handshake is completed, exposes the Control-M/Agent to vulnerabilities in the SSL/TLS implementation under certain non-default conditions (e.g. CVE-2025-55117 or CVE-2025-55118) or potentially to resource exhaustion.