Introduction
Until Build 6301, anyone who could reach a ManageEngine DDI Central console and knew the IP address of an onboarded Windows DNS or DHCP server could talk to the console as that server and create, change, or delete zones, records, and DHCP subnet data. Because a DDI platform sits upstream of name resolution and address assignment for an entire network, an integrity flaw at this layer shows up as redirected DNS traffic and disrupted DHCP management rather than a single compromised host.
DDI Central is ManageEngine's product for centrally managing DNS, DHCP, and IP address infrastructure, including Windows DNS and DHCP servers that report into a central console through node agents. ManageEngine is a division of Zoho Corp. The material we reviewed does not establish a DDI Central customer count or DDI market share, though the parent brand was named a Leader in the 2022 IDC MarketScape for unified endpoint management, a separate product category. Products in this class hold write authority over core naming and addressing data, which makes their internal trust boundaries, such as the console-to-agent channel affected here, a meaningful part of an organization's attack surface.
Technical Information
Root cause: a request body field used as identity
Build 6300 introduced the Windows Lightweight Node Agent. This agent reports DNS and DHCP state back to the DDI Central console through a set of agent sync API endpoints. In the affected builds, the console decided which agent was calling by reading a server_ip value from the HTTP request body.
The caller supplies that value, so the console was treating an unverified claim as a credential. ManageEngine's 6301 release notes describe the endpoints as exposed "with only server IP validation," and the advisory states that the endpoints did not adequately authenticate requests from Windows Node Agents. The CNA classifies this as CWE-306, Missing Authentication for Critical Function.
In practice, any client that supplies the IP address of an onboarded Windows DNS or DHCP server is treated as that server, and the console applies its synchronization requests to managed data.
Attack flow
Based on the vendor advisory, exploitation follows this sequence:
- The attacker obtains the IP address of a Windows DNS or DHCP server that has been onboarded into DDI Central. The advisory does not describe how an attacker would discover this.
- The attacker sends an HTTP request, without valid agent credentials, to one of the Windows DNS or DHCP agent sync endpoints on the console, setting
server_ipin the request body to the onboarded server's address. - The console attributes the request to that onboarded server and processes it as a legitimate synchronization operation.
- The attacker creates, modifies, or deletes DHCP subnet information, DNS zones, DNS zone scopes, and DNS records associated with the impersonated server.
The vendor has not published endpoint paths, a request example, or an exploit script, so we do not reproduce any request format here.
Impact
The advisory lists these consequences:
- Deletion or modification of DHCP subnet scopes
- Unauthorized DNS changes
- DNS traffic redirection
- Incorrect network configuration
- Disruption of DNS and DHCP management operations
The documented impact is unauthorized modification of managed network data. The vendor does not describe arbitrary command execution, credential theft, or compromise of the Windows servers themselves, and the sources do not support framing this as a general Windows DNS remote code execution issue.
CVSS breakdown
The CNA (ManageEngine) assigned a CVSS 3.1 base score of 9.1, Critical. NVD reproduces the CNA score and has not published a separate NIST assessment.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Confidentiality: None
- Integrity: High
- Availability: High
The score rests on integrity and availability, with no confidentiality impact. It does not tell you whether a given console is reachable from untrusted networks.
Timeline and exploitation status
The CNA reserved the ID on August 10, 2026. The vendor advisory dates the fix August 5, 2026, and the release notes list Build 6301 under August 4, 2026. NVD published the record on November 12, 2026. None of these dates indicates when the issue was discovered or first exploited.
The reviewed advisory and CNA record do not document active exploitation, a named threat actor, confirmed victims, a public proof of concept, or indicators of compromise. CISA KEV inclusion was not established in either direction. That gap reflects the limits of the available reporting and does not show that the issue has gone unexploited.
Patch Information
Fixed in: ManageEngine DDI Central Build 6301, shipped as the 6.3.1 service pack. ManageEngine's security index lists CVE-2026-19422 as fixed in Build 6301, and NVD (with ManageEngine as the CNA) marks every build below 6301 as affected. DDI Central is closed source, so no public commit or diff exists. The details below come from ManageEngine's advisory, release notes, and service pack page.
What the patch changes
The advisory says the fix enforces authentication and authorization checks on the affected agent sync endpoints. Requests are checked before any Windows DNS or DHCP sync operation is allowed, and requests without valid authentication or the required authorization are rejected before they reach the API handlers. The release notes summarize it as authentication and authorization "are enforced for the DNS/DHCP agent sync API endpoints."
The check runs in front of the sync handlers rather than inside each handler's business logic, so a request without credentials never reaches the code that creates, changes, or deletes zones, records, or subnet scopes.
Authentication and authorization are also separate steps. The caller must first prove it is a legitimate agent, then be permitted to perform sync operations, and identity no longer comes from a request body field. ManageEngine has not published the specific mechanism, such as per-agent tokens or credentials.
The issue was reported by qquynh.
Update both the console and the agents
Because the fix changes how the console and the Windows agent trust each other, both sides need updating. The advisory instructs customers to confirm afterward that the DDI Central Console and every applicable Windows Node Agent run the recommended versions. ManageEngine publishes separate 6300-to-6301 service packs per component, with these SHA256 values:
- Management UI Console, Linux:
ManageEngine_DDI_6_3_1_SP-6_3_1.ppm95d9cd2ee1910ca83e448646286b00c39891c6d604bccb15f9fba1e2cff4ef34 - Discovery Node Agent, Linux:
ManageEngine_DDIAGENT_6_3_1_SP-6_3_1.ppm531832fa67e905cf321c1434de1b67d3f625cf7177dcf194503efab0c859cd7e - Management UI Console, Windows:
ManageEngine_DDI_Windows_6_3_1_SP-6_3_1.ppmf4c9211d3e2140c400f6a9fd7d116e30f12a86237b71da12dc474df770168191 - Discovery Node Agent, Windows:
ManageEngine_DDIAGENT_Windows_6_3_1_SP-6_3_1.ppm623909f5ec16344396af66e8effd1e5b819f49d3823d42cc2776104f44617366
Upgrade sequencing
Service packs are applied in sequence, so older installs must step through each build. Build 6500 (September 17, 2026) follows 6301 in that chain and therefore also contains this fix. The service pack page gives these paths:
- Console or Discovery Node Agent at 6300: upgrade to 6301, then 6500.
- Console or Discovery Node Agent at 6301: upgrade to 6500.
- Earlier builds: identify the installed build (shown under the profile icon) and follow the matching sequence rather than assuming the 6300 path applies unchanged.
Applying the service pack
On Linux, as root, after downloading the service pack and manually backing up the installation directory:
systemctl stop DDI # back up the installation directory, then from the bin directory: sh UpdateManager.sh # provide the absolute path to the .ppm file sh PackageManager.sh systemctl start DDI
On Windows, stop the ManageEngine DDICentral service from the Services panel, back up the installation directory (the vendor states the database is backed up automatically), then from an administrator Command Prompt in the bin directory:
UpdateManager.bat REM provide the absolute path to the .ppm file PackageManager.bat
Restart the service afterward. Linux and Windows Discovery Node Agents can also be updated from the application interface. The vendor documents no temporary workaround, no CVE-specific firewall or WAF rule, no rollback procedure, and no downtime estimate.
Related fixes in the same releases
Build 6301 bundles roughly a dozen security fixes from the same researchers, many of them access control issues: cluster and subnet authorization on the lease APIs, permission checks on DNS zone scope deletion, and cross-cluster checks on Windows DHCP filters and options. Build 6500 continues the theme by adding authentication to the Linux Node Agent's keytab update. Several internal interfaces had been trusting callers by default, and these releases change that.
Discrepancies in vendor records
- The advisory page is titled CVE-2026-19422, but its CVE ID field reads CVE-2026-4734. NVD and ManageEngine's security index both tie this issue to CVE-2026-19422, so this appears to be a typo.
- The advisory rates the issue Critical, while the security index lists it as High. The CNA's CVSS 3.1 score on NVD is 9.1.
Affected Systems and Versions
- Product: Zohocorp ManageEngine DDI Central
- Affected: all builds below 6301 per the CNA record on NVD (the vendor advisory states build 6300 and lower)
- Vulnerable component: Windows DNS and DHCP agent synchronization APIs on the console, used by the Windows Lightweight Node Agent introduced in Build 6300
- Relevant configuration: deployments with onboarded Windows DNS or DHCP servers synchronizing through Windows Node Agents
- First fixed build: 6301 (6.3.1 service pack)
- Later build containing the fix: 6500
Remediation is complete only when the console and all applicable Windows Node Agents report the recommended versions.
Vendor Security History
Other ManageEngine products have a documented record of exploited vulnerabilities, which is useful context for patch adoption but is not evidence about this CVE:
- CVE-2021-44077, ServiceDesk Plus: an unauthenticated remote code execution flaw in versions through 11305. Zoho released a fix on September 16, 2021 (11306 and above), yet CISA and the FBI reported active exploitation on December 2, 2021, including webshell placement, administrator credential compromise, lateral movement, and exfiltration of registry hives and Active Directory files. The gap between fix availability and deployment is the relevant lesson.
- CVE-2022-47966, multiple on-premises products: remote code execution associated with Apache XML Security for Java 1.4.1. A September 7, 2023 CISA advisory documented nation-state APT actors exploiting it against a public-facing ServiceDesk Plus instance at an aeronautical sector organization, with indicators as early as January 2023, root-level access, creation of a local administrative user named
Azure, malware deployment, credential collection, and lateral movement.
Both cases involved remote code execution in a different product. CVE-2026-19422 is a missing authentication flaw that permits network configuration changes, and nothing in the reviewed sources links these campaigns or indicators to DDI Central.
References
- ManageEngine DDI Central security advisory for CVE-2026-19422
- NVD entry for CVE-2026-19422
- Official CVE record for CVE-2026-19422 (CVE Services API)
- ManageEngine DDI Central release notes
- ManageEngine DDI Central security updates index
- ManageEngine DDI Central service packs
- CISA and FBI alert on active exploitation of CVE-2021-44077 in ServiceDesk Plus
- CISA advisory AA23 250A on nation state exploitation of CVE-2022-47966
- ManageEngine Year in Review 2022



