Unauthorized debug API access via hardcoded credentials
Published Apr 10, 2026 · Updated Apr 10, 2026
Hard-coded credentials in BMC Control-M/MFT 9.0.20 through 9.0.22 allow remote attackers to access the MFT API debug interface. The application package stores a default debug username and password in cleartext, allowing the credentials to be extracted and presented to the interface. Exposure requires the credentials to remain unchanged; successful authentication grants unauthorized debug-interface access, while public records do not define the operations available there.
Summary
What happened
Hard-coded credentials in BMC Control-M/MFT 9.0.20 through 9.0.22 allow remote attackers to access the MFT API debug interface. The application package stores a default debug username and password in cleartext, allowing the credentials to be extracted and presented to the interface. Exposure requires the credentials to remain unchanged; successful authentication grants unauthorized debug-interface access, while public records do not define the operations available there.
The record
- CVE
- CVE-2026-23781
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, CAPEC-191, CAPEC-70, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo