Skip to main content
CVE-2025-55110VulnerabilityPublished

CVE-2025-55110: BMC Control-M/Agent · Use of Default Credentials

Affects BMC Control-M/AgentSource CVE Database V5

0

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
BMC Control-M/AgentAffected
  • =9.0.22
  • =9.0.21
  • =9.0.20
  • =9.0.19
  • =9.0.18
Fixed in–

AI-suggested

European organizations should immediately audit their Control-M/Agent deployments to identify affected versions (9.0.18 through 9.0.22). Since no patches are currently linked, organizations should implement the following specific mitigations: 1) Change the default keystore passwords to strong, unique passwords immediately after installation or upgrade. 2) Restrict file system permissions on keystore files to the minimum necessary, ensuring only authorized service accounts can read them. 3) Monitor and log access to keystore files to detect unauthorized read attempts. 4) Limit local access to systems running Control-M/Agent by enforcing strict access controls, including multi-factor authentication and network segmentation. 5) Conduct regular vulnerability scanning and penetration testing focused on local privilege escalation and file access controls. 6) Engage with BMC support for any available patches or recommended configurations to mitigate this vulnerability. 7) Educate system administrators about the risks of default credentials and enforce policies to change all default passwords in production environments.

Description

Control-M/Agents use a kdb or PKCS#12 keystore by default, and the default keystore password is well known and documented. An attacker with read access to the keystore could access sensitive data using this password.

References

Community reviews

Loading reviews…