What happened
ManageEngine, part of Zoho Corporation, has published security advisories for two vulnerabilities in DDI Central. It is a tool that companies and organizations use to centrally manage DNS, DHCP and IP address allocation (IPAM). The flaws are tracked as CVE-2026-95643 and CVE-2026-95645 and appeared in the NVD database on November 18, 2026.
According to the vendor, both were already fixed on September 17, 2026 in build 6500. The first flaw is in the Telnet connectivity check feature, the second in the Windows DDI Agent function that clears the list of blocked domains (clear_blocked_domains). In both cases, specially crafted input can lead to commands being executed on a managed Windows server.
The issues were reported by Zewei Zhang of NSFOCUS TIANJI Lab. Neither is listed in the CISA KEV catalog, and ENISA’s European Vulnerability Database EUVD (entries EUVD-2026-128487 and EUVD-2026-128488) does not report exploitation. The vendor’s advisories do not mention any attacks.
Why it is dangerous
Both flaws are command injection vulnerabilities (CWE-78). Imagine a form where you enter an address, which the system then pastes into an instruction for the computer. If the program does not check what is really in that address, someone can sneak in an extra instruction that the computer obediently carries out. In CVE-2026-95643 this was an IPv6 address with a so-called scope identifier that ended up inside a PowerShell command, in CVE-2026-95645 it was values in the blocked-domain list.
CVSS is an international 0 to 10 scale that rates how easy a flaw is to exploit and how much damage it can cause. Both flaws score CVSS 9.1, which falls into the critical band under CVSS 3.1. This score was not assigned by NVD itself but by the organization that submitted the vulnerability record. On its own website, the vendor rates both flaws as “High” severity.
- The attack works over the network and is not complex.
- The attacker must be logged in with high privileges. The vendor describes this as someone with access to the affected feature.
- No action from another user is needed.
- The impact reaches beyond DDI Central itself: commands run on managed Windows servers, with serious impact on confidentiality, integrity and availability.
What an attacker can gain depends on privileges. For CVE-2026-95643, the vendor says injected commands run under the Windows service account used for the operation and could read or modify system data, network configuration or services. For CVE-2026-95645, they run with the privileges of the DDI Agent process. The vendor classifies both as remote code execution (RCE).
Why this matters even though a login is required: DNS and DHCP are the heart of a network, and on Windows they often run directly on domain controllers. A stolen admin password or a misused account could therefore open a path to key servers. An EPSS score, which estimates the likelihood of exploitation, is not yet available for these flaws.
Who is affected
This affects organizations running ManageEngine DDI Central version 6.3.1 / Build 6301 or earlier. According to the NVD description, all builds below 6500 are affected. The vendor recommends updating both the DDI Central console and the agents on managed servers.
Both flaws target Windows servers: CVE-2026-95643 concerns managed Windows nodes, CVE-2026-95645 the Windows DDI Agent. The vendor strongly recommends the update for customers running DDI Agents on Windows. Typical environments are corporate networks, schools, hospitals and IT service providers where DDI Central manages DNS and DHCP servers.
You are not affected if you do not use DDI Central or already run build 6500 or later. The vendor does not list any other ManageEngine products in these advisories.
How to check if you are affected
You can find the build number in the DDI Central web console, usually in the product information (the help menu or “About”). If the build is lower than 6500, you are affected.
On Windows servers running the agent, this PowerShell command lists installed components and their versions. It only reads data from the registry:
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*, HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object { $_.DisplayName -like "*ManageEngine*" -or $_.DisplayName -like "*DDI*" } | Select-Object DisplayName, DisplayVersion
To see running agent services (the service name may differ):
Get-Service | Where-Object { $_.DisplayName -like "*DDI*" -or $_.DisplayName -like "*ManageEngine*" }
The build number in the console is what counts. Also list every server running an agent so none is missed during the update.
How to fix it
The fix is build 6500, released by the vendor on September 17, 2026. ManageEngine recommends updating the DDI Central console and the relevant agents (Node Agent, DDI Agent) to build 6500 or later using the corresponding service pack.
- List the console instance and every server running an agent. Windows servers come first.
- Before updating, back up the console and its database following the vendor’s documentation.
- Download the service pack for build 6500 or later from the ManageEngine website and update the DDI Central console first.
- Then update the agents on managed servers, starting with Windows.
- Confirm in the console and on the servers that build 6500 or later is running everywhere.
For CVE-2026-95645, the fix also restricts who can trigger the blocked-domain clearing function. Only the DDI Central application server can now do so, not the agent servers themselves.
The vendor does not list a workaround. Until you update, we recommend general measures: reduce the number of admin accounts in DDI Central, turn on multi-factor authentication if your environment supports it, and make the console reachable only from a management network or via VPN. Service accounts used by the Windows agent should have no more rights than they actually need.
What if you may already be compromised
The vendor has not published indicators of compromise and there are no reports of attacks. Still, if you ran an old build for a long time, a few places are worth checking.
- DDI Central users: unknown accounts, newly granted admin rights or logins from unusual addresses.
- Records of Telnet feature use and of changes to blocked-domain policies, especially unusual IPv6 addresses or strange domain values.
- Windows servers: new local accounts, new services, scheduled tasks and PowerShell logs, if logging is enabled.
These commands are read-only: they list local accounts, recently installed services and PowerShell log entries.
Get-LocalUser | Select-Object Name, Enabled, LastLogon
Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045} -MaxEvents 50
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-PowerShell/Operational'; Id=4104} -MaxEvents 50
If you find anything suspicious, do not delete files or reinstall the server, so you do not destroy evidence. Change the passwords of DDI Central admins and service accounts and bring in an incident response specialist, especially if the agent ran on a domain controller or under a highly privileged account.