Skip to main content
VulnerabilityPublished Updated

CVE-2025-55112: BMC Control-M/Agent · Use of Hard-coded Cryptographic Key

Affects BMC Control-M/AgentSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% 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:P/VC:H/VI:H/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 26 Oct 2026.

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. Upgrade to a supported version of BMC Control-M/Agent that does not use the Blowfish algorithm or does not contain the hardcoded key vulnerability.
  2. If upgrading is not immediately possible, disable the use of the Blowfish cryptographic algorithm in Control-M/Agent configurations and revert to default, secure encryption methods.
  3. Implement network segmentation and strict access controls to limit exposure of Control-M/Agent communication channels, reducing the risk of network traffic interception.
  4. Employ network-level encryption such as VPNs or TLS tunnels to protect Control-M traffic independently of the application-layer encryption.
  5. Monitor network traffic for unusual patterns or attempts to capture Control-M communications.
  6. Conduct regular audits of Control-M/Agent versions in use and enforce policies to retire unsupported software promptly.
  7. Educate users about the risks of interacting with untrusted network environments to reduce user interaction exploitation vectors.
  8. Engage with BMC support or security advisories for any forthcoming patches or workarounds.

Description

Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 (and potentially earlier unsupported versions) that are configured to use the non-default Blowfish cryptography algorithm use a hardcoded key. An attacker with access to network traffic and to this key could decrypt network traffic between the Control-M/Agent and Server.

References

Community reviews

Loading reviews…