CVE-2025-55108: BMC Control-M/Agent default configuration does not enforce SSL/TLS allowing unauthorized actions and remote code execution
BMC · Control-M/Agent
Vendor fix available · Affected: BMC Control-M/Agent · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 57% of scored CVEs
DescriptionCVE.org
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
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- BMC · Control-M/Agent9.0.22; 9.0.21; 9.0.20; 9.0.19; 9.0.18
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- BMC
- Published
- November 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-55108 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.