Skip to main content
CVE-2025-55111VulnerabilityPublished

CVE-2025-55111: BMC Control-M/Agent · Incorrect Default Permissions

Affects BMC Control-M/AgentSource CVE Database V5

0

Not known to be exploited · CVSS 5.7 Medium.

Data as of 25 Oct 2026, 19:02 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 2% 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-25.

What to do

Affected software

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

AI-suggested

1. Conduct an immediate audit of all Control-M/Agent installations to identify versions 9.0.18 through 9.0.20 and any earlier unsupported versions or upgraded systems from these versions. 2. Manually verify and correct file permissions on all sensitive files containing SSL keys, keystore, and policy data to restrict access strictly to the Control-M/Agent service account and system administrators only. 3. Implement strict local access controls and limit user privileges on systems running Control-M/Agent to reduce the risk of local exploitation. 4. Monitor local system access logs for unusual activity indicative of unauthorized local access attempts. 5. Engage with BMC support or official channels to obtain any forthcoming patches or guidance and plan for timely upgrades to supported, patched versions. 6. Consider isolating Control-M/Agent hosts in segmented network zones to limit lateral movement if compromise occurs. 7. Employ file integrity monitoring solutions to detect unauthorized changes to sensitive files. 8. Review and enhance endpoint security controls to prevent privilege escalation and unauthorized local access.

Description

Certain files with overly permissive permissions were identified in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions as well as in newer versions which were upgraded from an affected version. These files contain keys and passwords relating to SSL files, keystore and policies. An attacker with local access to the system running the Agent can access these files.

References

Community reviews

Loading reviews…