External risk intelligence

ManageEngine DDI Central PowerShell Command Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-95643

The vulnerability resides in a Telnet connectivity feature used for managing network nodes. While the product is a network management solution, this specific functionality is typically restricted to internal infrastructure administration rather than being exposed directly to the public internet.

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 security vulnerability has been identified in Zohocorp Manageengine DDI Central affecting its Telnet connectivity feature. This issue allows authenticated users to inject and execute commands on managed Windows nodes through specially crafted IPv6 scope identifiers. The primary concern is to confirm if this specific feature is in use within our environment.

  • Unauthenticated commands can run remotely.
  • Potentially impacts network device management.
  • Verify if Telnet feature is active.

Attack Path

How an attacker could exploit the issue

An attacker who has already gained authenticated access to ZohoCorp ManageEngine DDI Central could potentially exploit this vulnerability. By using the Telnet connectivity feature with specially crafted IPv6 scope identifiers, an attacker could inject and execute arbitrary PowerShell commands on the managed Windows nodes. This could lead to a complete compromise of the affected systems.

  • Requires authenticated access.
  • Triggers via specially crafted IPv6 scope identifiers.
  • Risk: Arbitrary command execution on managed nodes.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated attacker to execute arbitrary commands on managed Windows nodes when the Telnet connectivity feature is used with specially crafted IPv6 scope identifiers. This could impact the integrity and availability of system data and services on those nodes.

  • Managed Windows nodes.
  • Through Telnet feature with crafted IPv6 identifiers.
  • Arbitrary command execution on nodes.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

For this authenticated PowerShell command injection vulnerability in Manageengine DDI Central's Telnet connectivity feature, the platform or infrastructure teams managing the DDI Central deployment are likely the first point of contact. They should initiate the process by identifying all instances of the affected product, determining their network reachability and business criticality, and locating the accountable system owner. Remediation planning will then proceed based on the assessed risk.

  • Platform/Infrastructure teams own remediation.
  • Verify affected DDI Central instances and reachability.
  • Plan remediation based on business criticality.

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 by organizations to centralize the administration of DNS, DHCP, and IP address management (IPAM). It helps IT teams manage IP resources across their infrastructure, including the ability to communicate with and oversee managed Windows nodes through various protocols like Telnet.

What does the CVE-2026-95643 vulnerability mean?

This vulnerability is a form of OS Command Injection (CWE-78). It means the application does not properly sanitize input, allowing a user to inject malicious PowerShell commands into the system. In this specific case, these commands are executed on managed Windows nodes via the product's Telnet connectivity feature.

How is the command injection triggered?

The vulnerability is triggered when a user with existing access to the application utilizes the Telnet connectivity feature with a specially crafted IPv6 scope identifier. It is important to note that standard network traffic or typical administrative use of the Telnet feature without these specific malformed IPv6 identifiers will not trigger the bug.

Is my DDI Central instance at risk?

According to Halo Surface Signal, risk is considered unlikely for most because the vulnerable Telnet feature is typically used for internal infrastructure administration rather than being exposed to the public internet. If your instance is kept within an internal, restricted management network, the practical likelihood of exploitation by external actors is significantly reduced.

What should I do if I use this software?

First, verify if your DDI Central deployment is running a build earlier than 6500, as these are the only versions affected. Confirm whether your team actively utilizes the Telnet connectivity feature for managing Windows nodes. If you use this feature, prioritize auditing your current build status and coordinate with your infrastructure team to plan necessary updates.

References