# CVE-2026-101207: Command injection in OpenManage Integration

> A low-privileged remote attacker can execute arbitrary OS commands in Dell OpenManage Integration for Windows Admin Center.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-5jqw-c6mx-h53q

## What is CVE-2026-101207?

CVE-2026-101207 is a high-severity command injection vulnerability in Dell OpenManage Integration, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dell OpenManage Integration with Microsoft Windows Admin Center, versions prior to 3.7.0, contains an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Remote execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-101207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101207 is a high-severity command injection vulnerability in Dell OpenManage Integration, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101207 in the wild and no public exploit code.

Affected product: Dell OpenManage Integration. 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-101207/ (Markdown: https://insights.sbomify.com/CVE-2026-101207/index.md)
```

## Sources

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

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