An unauthenticated remote attacker could impersonate an onboarded Windows server and submit unauthorized synchronization requests.ManageEngine labels its individual advisory Critical, while its DDI Central security list labels the same CVE High. It fixed the flaw in build 6301 on August 5, 2026. The NVD record, published November 12, 2026, lists a CVSS 3.1 score of 9.1.
What it allows
How Can CVE-2026-19422 Change DNS and DHCP Data?
ManageEngine says the affected synchronization functions did not adequately authenticate Windows Node Agent requests. The application trusted a server identity supplied by the requester, allowing an outsider to impersonate an onboarded Windows DNS or DHCP server.
A successful request could create, change, or delete DHCP subnet information, DNS zones, zone scopes, and records tied to that server. ManageEngine says the resulting changes could redirect DNS traffic, misconfigure networks, or disrupt DNS and DHCP management.
The NVD CVSS 3.1 vector assigns high integrity and availability impacts, with no confidentiality impact. This is a possible outcome of the flaw, rather than a confirmed incident.
From August 14 through November 12, 2026, Brandefense Blackhole recorded 2 dark-chat posts matching CVE-2026-19422. That is a count of discussion posts and does not establish active exploitation.
CVE-2026-19422 was absent from CISA's KEV catalog version 2026.11.10. The catalog snapshot predates NVD publication, so it cannot establish the vulnerability's current exploitation status.
For related product information, see Brandefense's vulnerability intelligence platform. The DNS hijacking glossary explains the impact of unauthorized DNS redirection.
Who is affected
Which DDI Central Builds Are Affected by CVE-2026-19422?
ManageEngine lists DDI Central version 6.3.0, build 6300, and lower as affected. Build 6301 is the vendor's fixed release.
The affected operation is Windows DNS and DHCP agent synchronization. Inventory DDI Central installations that manage onboarded Windows DNS or DHCP servers, then check the running build in each console.
ManageEngine instructs customers to install the applicable service pack and verify both the console and all applicable Windows Node Agent instances. Because the fix depends on the installed service pack and agent state, confirm the running versions manually after maintenance.
Brandefense's external attack surface management platform scans internet-facing assets. That inventory step complements the vendor's build check; the service pack remains the fix.
Timeline
- 2026-08-05
ManageEngine says it fixed CVE-2026-19422 in DDI Central build 6301.
- 2026-11-12
NVD published the CVE record and listed CVSS 3.1 9.1 Critical.
What to do
-
Inventory DDI Central consoles and Windows agents
Identify installations running build 6300 or lower and the onboarded Windows DNS or DHCP servers they manage. Prioritize consoles reachable from untrusted networks.
-
Install ManageEngine build 6301
Apply the applicable DDI Central service pack to reach build 6301. Follow ManageEngine's upgrade instructions for the deployment.
-
Verify console and agent versions
After the upgrade, confirm the DDI Central Console and every applicable Windows Node Agent runs the vendor-recommended version. Recheck the installed build before closing the change.
-
Review DNS and DHCP changes
As a Brandefense defensive recommendation, examine synchronization activity and DNS or DHCP changes for unexplained updates. Investigate any unauthorized changes and preserve relevant logs.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-19422 in Brandefense Atlas
The Atlas record of CVE-2026-19422: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-19422?
It is an authentication bypass in ManageEngine DDI Central's Windows DNS and DHCP agent synchronization. An unauthenticated attacker could impersonate an onboarded Windows server and alter related DNS or DHCP data.
Which DDI Central build fixes CVE-2026-19422?
ManageEngine lists build 6301 as the fix. Install the applicable service pack, then verify the console and all applicable Windows Node Agents.
Which installations need attention?
ManageEngine lists DDI Central version 6.3.0, build 6300, and lower. Focus on installations managing onboarded Windows DNS or DHCP servers.
Is active exploitation confirmed?
Brandefense Blackhole counted 2 matching dark-chat posts from August 14 through November 12, 2026. Discussion posts are not evidence of attacks. CISA KEV catalog version 2026.11.10 did not list the CVE.
What is the CVSS score?
NVD lists CVSS 3.1 9.1 Critical as a secondary score attributed to the CNA identifier. ManageEngine labels its individual advisory Critical without a numeric score.
Sources
- ManageEngine DDI Central Security Update CVE-2026-19422ManageEngine
- DDI Central Security Updates ListManageEngine
- CVE-2026-19422 DetailNational Vulnerability Database
- Known Exploited Vulnerabilities CatalogCISA