# CVE-2025-55109: BMC Control-M/Agent default SSL/TLS configuration authenticated bypass

> Remote attackers can bypass authentication on BMC Control-M/Agent by using default or empty keystores with trusted third-party certificates.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 26 Feb 2026
- **Also known as:** GHSA-gh47-wqwg-v2cm

## What is CVE-2025-55109?

CVE-2025-55109 is a critical authentication bypass 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

An authentication bypass vulnerability exists in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions when using an empty or default kdb keystore or a default PKCS#12 keystore. A remote attacker with access to a signed third-party or demo certificate for client authentication can bypass the need for a certificate signed by the certificate authority of the organization during authentication on the Control-M/Agent.

The Control-M/Agent contains hardcoded certificates which are only trusted as fallback if an empty kdb keystore is used; they are never trusted if a PKCS#12 keystore is used. All of these certificates are now expired.

In addition, the Control-M/Agent default kdb and PKCS#12 keystores contain trusted third-party certificates (external recognized CAs and default self-signed demo certificates) which are trusted for client authentication.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Bmc Control-M\/Agent.

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

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

## Is CVE-2025-55109 being exploited?

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

## Other vulnerabilities in BMC Control-M/Agent

- [CVE-2025-55113](https://insights.sbomify.com/CVE-2025-55113/): BMC Control-M/Agent unescaped NULL byte in access control list checks (critical 9.5)
- [CVE-2025-55115](https://insights.sbomify.com/CVE-2025-55115/): BMC Control-M/Agent path traversal local privilege escalation (critical 9.3)
- [CVE-2025-55116](https://insights.sbomify.com/CVE-2025-55116/): BMC Control-M/Agent buffer overflow local privilege escalation (critical 9.3)
- [CVE-2025-55112](https://insights.sbomify.com/CVE-2025-55112/): BMC Control-M/Agent hardcoded Blowfish keys (high 7.6)
- [CVE-2025-55117](https://insights.sbomify.com/CVE-2025-55117/): BMC Control-M/Agent buffer overflow in SSL/TLS communication (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55109 is a critical authentication bypass 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-55109 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-55109/ (Markdown: https://insights.sbomify.com/CVE-2025-55109/index.md)
```

## Sources

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

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