dbcve.org
Control M\/agentApplication · Bmc

CVE-2025-55111

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-16
Fix available
A fix is available. Upgrade to 9.0.21 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain files with overly permissive permissions were identified in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions as well as in newer versions which were upgraded from an affected version. These files contain keys and passwords relating to SSL files, keystore and policies. An attacker with local access to the system running the Agent can access these files.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Control-M/Agent versions 9.0.18 through 9.0.20 (and potentially earlier unsupported versions, including upgrades from affected versions) ship with SSL key files, keystores, and policy password files configured with overly permissive permissions. A local attacker with access to the system can read these sensitive credential files containing SSL keys and passwords.

MitigationIdentify and restrict file permissions on all SSL/keystore/policy files in affected Control-M/Agent installations to the service account only; rotate any exposed credentials as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Control M\/agentApplication
Affected:< 9.0.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Control-M/Agent version
    Run the command to check the installed Control-M/Agent version, such as 'ctmversion' or check the installation directory for version information
    Affected if The installed version is 9.0.18, 9.0.19, or 9.0.20, or any version prior to 9.0.21 that was upgraded from an affected version
  2. Locate SSL key and keystore files
    Search for common SSL key files (.key, .pem), keystores (.jks, .keystore), and truststores in the Control-M/Agent installation directory and subdirectories
    Affected if Any SSL key files or keystores exist in the Control-M/Agent installation path
  3. Locate policy password files
    Search for policy configuration files that may contain embedded passwords, typically found in Control-M/Agent configuration directories
    Affected if Policy configuration files with embedded passwords exist in the Control-M/Agent installation
  4. Verify file permissions on sensitive credential files
    Use 'ls -la' or 'icacls' (Windows) to examine permissions on all identified SSL key files, keystores, and policy password files
    Affected if Any of these sensitive files are readable by users other than the Control-M service account (e.g., have world-readable, group-readable, or overly broad ACL permissions)

You are affected if Control-M/Agent version is below 9.0.21 AND sensitive credential files (SSL keys, keystores, policy password files) are readable by non-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.21 or later
Fixed in 9.0.21
Interim mitigation

Identify and restrict file permissions on all SSL/keystore/policy files in affected Control-M/Agent installations to the service account only; rotate any exposed credentials as a precautionary measure.

Recommended fix Moderate confidence

Control-M/Agent version 9.0.21 or later (latest supported release)

  1. 1. Verify current Control-M/Agent version by checking the installed version on affected systems
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up the current Control-M/Agent configuration, including any custom policies, SSL keys, and keystore files
  4. 4. Download Control-M/Agent version 9.0.21 or later from the official BMC support site (bmcapps.my.site.com)
  5. 5. Stop the Control-M/Agent services before upgrading
  6. 6. Install the Control-M/Agent 9.0.21 (or latest supported version) using the standard upgrade procedure
  7. 7. Verify that the new version is running correctly and that services have started successfully
  8. 8. Confirm that file permissions on SSL keys, keystore, and policy files have been corrected to restrictive permissions (typically 600 or stricter for sensitive files)
Caveat Review release notes for version 9.0.21 to check for any configuration or behavioral changes that may affect existing jobs; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control M\/agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55111 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data