CVE-2025-55112: BMC Control-M/Agent hardcoded Blowfish keys

Published Sep 16, 2025
·
Updated

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.

Affected Software

2 affected components
BMC Control-M/Agent>=9.0.18<=9.0.20
BMC Control-m\/agent<=9.0.20.200

Event History

Sep 16, 2025
CVE Published
via MITRE·12:19 PM
Data Sourced
via MITRE·12:19 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-55112?

CVE-2025-55112 has a critical severity due to the potential for attackers to decrypt sensitive network traffic.

2

How do I fix CVE-2025-55112?

To mitigate CVE-2025-55112, upgrade to a supported version of Control-M/Agent that does not use the hardcoded Blowfish key.

3

What versions are affected by CVE-2025-55112?

CVE-2025-55112 affects BMC Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions.

4

What risks are associated with CVE-2025-55112?

The risks associated with CVE-2025-55112 include potential unauthorized decryption of sensitive data transmitted over the network.

5

Is there a workaround for CVE-2025-55112?

There are no specific workarounds for CVE-2025-55112, and upgrading to a secure version is the recommended course of action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203