# CVE-2026-12267: Authenticated PowerShell Injection in DNS Query Resolution Policy leads to RCE

> Authenticated attackers can inject PowerShell commands into DNS policy names to achieve remote code execution on ManageEngine DDI Central servers.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-4mg5-mmrj-mrfc

## What is CVE-2026-12267?

CVE-2026-12267 is a high-severity command injection vulnerability in Zohocorp DDI Central, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ManageEngine DDI Central versions below 6201 are vulnerable to Command injection in Windows DNS Query Resolution Policy name field leading to remote code execution.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-12267 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12267 is a high-severity command injection vulnerability in Zohocorp DDI Central, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12267 in the wild and no public exploit code.

Affected product: Zohocorp DDI Central. 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-12267/ (Markdown: https://insights.sbomify.com/CVE-2026-12267/index.md)
```

## Sources

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

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