# CVE-2025-55110: BMC Control-M/Agent hardcoded default keystore password

> Attackers with file access can decrypt sensitive data using the well-known default keystore password in BMC Control-M Agents.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** GHSA-799r-mf4m-6j6w

## What is CVE-2025-55110?

CVE-2025-55110 is a medium-severity vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Control-M/Agents use a kdb or PKCS#12 keystore by default, and the default keystore password is well known and documented.

An attacker with read access to the keystore could access sensitive data using this password.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2025-55110 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55110 is a medium-severity vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55110 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-55110/ (Markdown: https://insights.sbomify.com/CVE-2025-55110/index.md)
```

## Sources

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

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