External risk intelligence

ManageEngine DDI Central Authenticated Command Injection in Windows DDI Agent

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-95645

The vulnerability exists within a specific agent component (Windows DDI Agent) and requires authentication to exploit. While the product is a network management tool, the agent's functionality is typically restricted to internal infrastructure management rather than being directly exposed to the public internet. Access is generally controlled and limited to internal administrative environments.

OS Command Injection

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in ManageEngine DDI Central, specifically affecting its Windows DDI Agent. This issue allows authenticated users to execute arbitrary commands on affected Windows systems by manipulating certain domain-blocking functions.

  • Authenticated command execution in DDI Agent.
  • Confirms a potential attack vector for internal systems.
  • Verify product relevance and confirm exposure.

Attack Path

How an attacker could exploit the issue

An attacker with administrative access to ManageEngine DDI Central could exploit this vulnerability by sending specially crafted requests to the Windows DDI Agent. By manipulating the blocked-domain values, an attacker could trick the agent into executing arbitrary commands on the underlying Windows system. This could allow them to take full control of the compromised system, potentially leading to further network compromise.

  • Requires authenticated access to DDI Central.
  • Triggers arbitrary command execution via blocked-domain values.
  • Risk of full system compromise.

Live Threat

Current exploitation, exposure, and threat context

An authenticated command injection vulnerability in the Windows DDI Agent's `clear_blocked_domains` functionality could allow specially crafted blocked-domain values to trigger arbitrary command execution on Windows systems, when supported by the advisory.

  • System data on Windows agents.
  • Specially crafted input can execute commands.
  • Unrestricted command execution on systems.

Operational Fix

Recommended remediation, mitigation, and detection steps

This authenticated command injection vulnerability impacts ManageEngine DDI Central's Windows DDI Agent, potentially allowing arbitrary code execution by authenticated users. The first practical step is for infrastructure or platform teams to locate all instances of the affected agent, confirm its reachability and business criticality, and then engage the accountable application owner to plan remediation.

  • Identify and verify affected agents.
  • Confirm operational criticality and exposure.
  • Plan remediation with application owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Zohocorp ManageEngine DDI Central?

ManageEngine DDI Central is a network management solution used to oversee and automate DNS, DHCP, and IP address management (DDI). The software utilizes specialized agents—such as the Windows DDI Agent—to perform administrative tasks and enforce configuration policies directly on endpoint servers across an enterprise network infrastructure.

What does command injection mean for CVE-2026-95645?

This vulnerability is classified as CWE-78, or OS Command Injection. It occurs when an application improperly filters input before passing it to a system shell. In this case, the Windows DDI Agent fails to sanitize blocked-domain values, allowing an attacker to inject and execute their own unauthorized system commands with the privileges of the agent.

How is this vulnerability triggered?

An attacker must be able to send specifically formatted data to the clear_blocked_domains function within the Windows DDI Agent. This bug is not triggered by standard, legitimate network traffic or typical administrative configuration changes; it requires deliberate manipulation of input values to force the system to execute unintended commands.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal indicates that exploitation is unlikely for most environments. Because the Windows DDI Agent is designed for internal infrastructure management, it is typically not exposed to the public internet. The requirement for authenticated access further limits the attack surface to users who already have authorized entry into the management system.

What should I do if I run ManageEngine DDI Central?

Your first step is to perform an inventory of your environment to identify all servers running the affected Windows DDI Agent. Once these instances are located, verify which systems are running build versions earlier than 6500. Finally, coordinate with your application administrators to prioritize these specific assets for the necessary software updates.

References