CVE
Zoho DDI Central authorization bypass in DHCP subnet options
- Exploited
- No known exploitation
- Fix
- Fixed in 6301
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects DDI Central 6.3.0 build 6300 Involves the Windows DHCP option configuration workflow Attacker must be an operator with access to one DDI Central cluster
- 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
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 1.12% · 66th percentile
- 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? →
- 16/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? →
- Specific setups only
- 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 authorization bypass that lets a logged-in user with non-administrative rights change DHCP options on subnets that belong to clusters they are not authorized for. The attack can be carried out remotely over the network, and it requires only a low-privilege account and no user interaction.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Zohocorp ManageEngine DDI Central versions below 6301 is affected by an authorization bypass vulnerability that allowed authenticated non-administrative users to modify DHCP options on subnets belonging to unauthorized clusters.
Who should check
Teams running ManageEngine DDI Central 6.3.0 build 6300 with Windows DHCP subnets managed across multiple clusters, plus any non-admin operators with cluster-scoped access
Read the source excerpt
“ManageEngine DDI Central 6.3.0 build 6300 had an authorization vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects DDI Central 6.3.0 build 6300 Involves the Windows DHCP option configuration workflow Attacker must be an operator with access to one DDI Central clusterUpgrade 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-75868 (Broken Access Control), 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-75868 (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):
- Affects DDI Central 6.3.0 build 6300 (source: https://www.manageengine.com/ca/dns-dhcp-ipam/security-updates/cve-2026-75868.html)
- Involves the Windows DHCP option configuration workflow (source: https://www.manageengine.com/ca/dns-dhcp-ipam/security-updates/cve-2026-75868.html)
- Attacker must be an operator with access to one DDI Central cluster (source: https://www.manageengine.com/ca/dns-dhcp-ipam/security-updates/cve-2026-75868.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-75868 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75868 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/ca/dns-dhcp-ipam/security-updates/cve-2026-75868.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-75868
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-75868"}.Timeline
- CVE published
- First seen 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-75868
Is CVE-2026-75868 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 authorization flaw in the Windows DHCP option configuration workflow lets an authenticated operator replace the DNS Server DHCP option of a Windows subnet in an inaccessible cluster. Clients could then be directed to an unauthorized DNS resolver, which may disrupt name resolution or traffic.Source: manageengine.com
Which versions are affected by CVE-2026-75868?
DDI Central: before 6301.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists DDI Central 6.3.0 build 6300 as affected, and the affected setup involves the Windows DHCP option configuration workflow with an operator who has access to one DDI Central cluster. Check the installed DDI Central version and build number against 6.3.0 build 6300.Source: manageengine.com
How do I fix CVE-2026-75868?
Upgrade to a fixed version: 6301. The vendor's advisory also recommends Build 6301 or later.Source: cve.now feed data, manageengine.com