Skip to main content
Menu
CVEs

CVE

Zoho DDI Central authorization bypass in Windows DHCP filter settings

CVE-2026-75867EUVD-2026-124372

8.1HighCNA
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. Product is DDI Central 6.3.0 build 6300 Windows DHCP filter-list configuration workflow is in use Attacker is an authenticated non-administrator operator with access to one cluster

Published
Last modified
Reference
Last checked
1.12% · 66th percentile
16/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Zohocorp ManageEngine DDI Central has an authorization bypass that lets a logged-in user with ordinary, non-administrative rights change Windows DHCP filter-list settings for clusters they should not control. An attacker can reach it remotely over the network with low-privileged credentials and no action from anyone else.

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 Windows DHCP filter-list configurations across unauthorized clusters.

Who should check

Teams running ManageEngine DDI Central 6.3.0 build 6300 that manage Windows DHCP servers across multiple clusters.

Read the source excerpt

“Affected Software Version(s): DDI Central 6.3.0 / Build 6300”

manageengine.com

cve.now Index

16Pcve.now Index 16 of 100 · methodology v3 · provisional
  • 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.

    Product is DDI Central 6.3.0 build 6300 Windows DHCP filter-list configuration workflow is in use Attacker is an authenticated non-administrator operator with access to one cluster
  • 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-75867 (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-75867 (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):
- Product is DDI Central 6.3.0 build 6300 (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75867.html)
- Windows DHCP filter-list configuration workflow is in use (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75867.html)
- Attacker is an authenticated non-administrator operator with access to one cluster (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-75867.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-75867 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75867 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-75867.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-75867
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-75867"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Zohocorp DDI Central

    fixed in 6301

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-75867

Is CVE-2026-75867 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 authenticated operator with non-administrator access to one cluster can enable or disable the Windows DHCP allow and deny lists of a server in a cluster they cannot access. This changes DHCP admission controls.Source: manageengine.com

Which versions are affected by CVE-2026-75867?

DDI Central: before 6301.Source: cve.now feed data

Am I affected, and how do I check?

The advisory names DDI Central 6.3.0 build 6300, and the flaw sits in the Windows DHCP filter-list configuration workflow. To check a build, look at the DDI Central version or build number in the product's version information.Source: manageengine.com

How do I fix CVE-2026-75867?

Upgrade to a fixed version: 6301. The vendor's advisory also recommends Build 6301 or later.Source: cve.now feed data, manageengine.com