# CVE-2026-10537: Remote unauthenticated information disclosure and denial of service due to unauthenticated service access


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026

## What is CVE-2026-10537?

CVE-2026-10537 is a medium-severity vulnerability in BMC Control-M/Enterprise Manager, published on 27 Oct 2026. 

### Official description

A misconfiguration issue in the affected service in Control-M/Enterprise Manager and Control-M/Server may allow unauthenticated remote users to access certain service functionality, which could potentially result in information exposure or affect service availability.

This vulnerability affects :

  *  Control-M/Enterprise Manager versions 9.0.20 to 9.0.22 (excluded) and potentially earlier unsupported versions.
  *  Control-M/Server versions 9.0.20 to 9.0.22 (excluded) and potentially earlier unsupported versions

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

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

## Is CVE-2026-10537 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10537 is a medium-severity vulnerability in BMC Control-M/Enterprise Manager, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-10537 in the wild and no public exploit code.

Affected product: BMC Control-M/Enterprise Manager. 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-10537/ (Markdown: https://insights.sbomify.com/CVE-2026-10537/index.md)
```

## Sources

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

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