# CVE-2026-23782: Information disclosure in n/a

> Unauthenticated attackers can retrieve API secrets from BMC Control-M/MFT, enabling unauthorized privileged API access and potential system compromise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-83mf-f2q6-j3gg

## What is CVE-2026-23782?

CVE-2026-23782 is a high-severity vulnerability in n/a, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in BMC Control-M/MFT 9.0.20 through 9.0.22. An API management endpoint allows unauthenticated users to obtain both an API identifier and its corresponding secret value. With these exposed secrets, an attacker could invoke privileged API operations, potentially leading to unauthorized access.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-23782?

It affects 1 product.


Products: Bmc Control-M\/Managed File Transfer.

## How do I fix CVE-2026-23782?

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

## Is CVE-2026-23782 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-23781](https://insights.sbomify.com/CVE-2026-23781/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2026-23780](https://insights.sbomify.com/CVE-2026-23780/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23782 and fix it if it is affected.

What it is: CVE-2026-23782 is a high-severity vulnerability in n/a, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23782 in the wild and no public exploit code.

Affected product: n/a. 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-2026-23782/ (Markdown: https://insights.sbomify.com/CVE-2026-23782/index.md)
```

## Sources

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

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