dbcve.org
Control M\/managed File TransferApplication · Bmc

CVE-2026-23781

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-10
Fix available
A fix is available. Upgrade to after 9.0.22 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
An issue was discovered in BMC Control-M/MFT 9.0.20 through 9.0.22. A set of default debug user credentials is hardcoded in cleartext within the application package. If left unchanged, these credentials can be easily obtained and may allow unauthorized access to the MFT API debug interface.

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

Hardcoded cleartext default debug credentials are embedded in the BMC Control-M/MFT application package versions 9.0.20 through 9.0.22. Attackers who obtain these credentials can directly access the MFT API debug interface without authentication, potentially allowing full compromise of the MFT system.

MitigationContact BMC for an emergency patch to replace hardcoded credentials. Immediately disable or restrict access to debug interfaces and rotate any exposed credentials if discoverable. Implement network segmentation to limit debug interface exposure until patch is applied.

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\/managed File TransferApplication
Affected:>= 9.0.20, <= 9.0.22

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify Control-M/MFT version
    Run 'mftcmd -version' or check the installation directory for version file, or inspect the package metadata in the installation path
    Affected if Installed version is 9.0.20, 9.0.21, or 9.0.22
  2. Locate debug interface configuration
    Search for debug-related configuration files in the MFT installation directory, typically under config/ or conf/ subdirectories, and look for files containing 'debug' or 'api' in the name
    Affected if Debug interface configuration files exist and are present in the installation
  3. Check for hardcoded credentials in config files
    Examine configuration files for cleartext username/password pairs, particularly in debug-related XML, properties, or config files. Look for default or hardcoded credential patterns
    Affected if Cleartext default credentials are found embedded in configuration files
  4. Verify debug port exposure
    Check network listener configuration and firewall rules for any debug API ports (commonly 8443, 8080, or custom debug ports) that may be exposed externally
    Affected if Debug interface port is accessible from network locations outside localhost

You are affected if you are running Control-M/MFT versions 9.0.20 through 9.0.22 and the debug interface is enabled or accessible with default credentials.

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 a release after 9.0.22
Vendor patch docs.bmc.com →
Interim mitigation

Contact BMC for an emergency patch to replace hardcoded credentials. Immediately disable or restrict access to debug interfaces and rotate any exposed credentials if discoverable. Implement network segmentation to limit debug interface exposure until patch is applied.

Recommended fix High confidence

Control-M/MFT 9.0.22 with patch PAAFP-9-0-22-025 applied

  1. Access the vendor patch URL: https://docs.bmc.com/xwiki/bin/view/Control-M-Orchestration/Control-M/ctm9022/Patches/Control-M-MFT-PAAFP-9-0-22-025/
  2. Review the patch documentation for Control-M-MFT-PAAFP-9-0-22-025
  3. Apply the patch following BMC's documented installation procedures
  4. After patching, change any default credentials that may have been hardcoded
  5. Verify the patch was applied successfully
  6. Confirm the debug interface is no longer accessible with default credentials

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

Fix this in Control M\/managed File Transfer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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