dbcve.org
Control M\/agentApplication · Bmc

CVE-2025-55116

HIGH · 8.8 CVSS v3.1 Published 2025-09-16
Fix available
A fix is available. Upgrade to 9.0.20.100 or later.
See remediation →
90/100
Remediation priority · Urgent
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
A buffer overflow in the Control-M/Agent can lead to a local privilege escalation when an attacker has access to the system running the Agent. This vulnerability impacts the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions.

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 · moderate confidence

A buffer overflow vulnerability in BMC Control-M/Agent versions 9.0.18 through 9.0.20 allows a local attacker with system access to execute arbitrary code and escalate privileges, likely by overflowing a stack or heap buffer in the agent process.

MitigationUpgrade Control-M/Agent to a supported version; if immediate upgrade is not feasible, restrict physical and logical access to systems running the agent and monitor for exploitation indicators.

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.20.100

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate Control-M/Agent installation directory
    Search for Control-M installation folders: on Linux/Unix check /opt/control-m/agent, /opt/control-m/, or run 'find /opt -name "*control*" -type d 2>/dev/null'; on Windows check C:\Program Files\BMC Software\Control-M Agent or use registry key HKLM\SOFTWARE\BMC Software\Control-M
    Affected if The Control-M/Agent software is found installed on the system
  2. Identify installed agent version
    Look for version file in the installation directory (commonly named version.txt, VERSION, or .version) or run version command if available (ctmversion, ctmadmin --version, or agent --version in the bin folder)
    Affected if Cannot determine the version - manual inspection of version information is required
  3. Compare version to affected range
    Parse the version number found (format appears to be 9.0.x.x) and compare against 9.0.20.100 - any version less than 9.0.20.100 is affected
    Affected if Installed version is lower than 9.0.20.100 (for example: 9.0.18, 9.0.19, 9.0.20, 9.0.20.50, etc.)
  4. Verify agent process is running
    Check for running agent processes: on Linux/Unix run 'ps -ef | grep -i "ctm"' or 'ps -ef | grep -i "control-m"'; on Windows run 'tasklist | findstr /i "ctm"' or check Windows Services for Control-M Agent service
    Affected if The agent process/service is actively running - this enables local privilege escalation if exploited

The system is affected if BMC Control-M/Agent is installed with any version lower than 9.0.20.100 and the agent is running or installed on the target system.

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.20.100 or later
Fixed in 9.0.20.100
Interim mitigation

Upgrade Control-M/Agent to a supported version; if immediate upgrade is not feasible, restrict physical and logical access to systems running the agent and monitor for exploitation indicators.

Recommended fix High confidence

Control-M/Agent version 9.0.20.100 or later

  1. 1. Identify the current Control-M/Agent version by running: ctmversion or checking the agent installation directory
  2. 2. Plan upgrade to Control-M/Agent version 9.0.20.100 or later
  3. 3. Review BMC Control-M release notes and upgrade documentation for version 9.0.20.100
  4. 4. Create a full backup of the Control-M/Agent configuration directory
  5. 5. Stop the Control-M/Agent service before upgrading
  6. 6. Download the Control-M/Agent installation package for version 9.0.20.100 or later from BMC (https://bmcapps.my.site.com)
  7. 7. Run the installer as administrator to upgrade the agent
  8. 8. Restart the Control-M/Agent service after upgrade completes
Caveat Upgrading from very old out-of-support versions may require careful compatibility checking; review BMC migration guides for your specific version range

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

Fix this in Control M\/agent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55116 — 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-55116 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