CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6301
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6301.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
Who should check
Teams running Zohocorp ManageEngine DDI Central build 6300 or lower with Windows DNS or DHCP servers onboarded to it.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6301.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Zohocorp DDI Central
fixed in 6301
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-19422
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: cve.now feed data
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: manageengine.com
Which versions are affected by CVE-2026-19422?
DDI Central: before 6301.Source: cve.now feed data
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: manageengine.com
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: manageengine.com