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

> Remote attackers can trigger memory corruption in BMC Control-M/Agent via SSL/TLS communication when specific non-default configurations are enabled.

- **Severity:** High 8.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 18 Nov 2025
- **Also known as:** GHSA-r54c-3jgv-4vr7

## What is CVE-2025-55118?

CVE-2025-55118 is a high-severity memory corruption vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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"

Weakness: CWE-787 (Out-of-bounds Write), CWE-665 (Improper Initialization), CWE-416 (Use After Free), CWE-415 (Double Free), CWE-191 (Integer Underflow (Wrap or Wraparound)), CWE-125 (Out-of-bounds Read), CWE-835 (Loop with Unreachable Exit Condition), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-55118?


## How do I fix CVE-2025-55118?

No fix has been published for CVE-2025-55118 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55118 being exploited?

There is no known exploitation of CVE-2025-55118 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55118 and fix it if it is affected.

What it is: CVE-2025-55118 is a high-severity memory corruption vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55118 in the wild and no public exploit code.

Affected product: BMC Control-M/Agent. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55118/ (Markdown: https://insights.sbomify.com/CVE-2025-55118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55118
- OSV: https://osv.dev/vulnerability/CVE-2025-55118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55118/
Summaries are generated and may contain mistakes; the official description above is the record.