CVE
Broken Access Control
- 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 version 6.3.0 build 6300 and below. The flaw is in the Windows DNS zone-scope management API, specifically the zone deletion endpoint.
- 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? →
- 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 a broken access control flaw that lets a logged-in user with ordinary, non-administrator rights delete DNS zones outside the scope they were assigned. The attacker can reach it remotely over the network and needs only low-privilege login, with no action required 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 improper authorization vulnerability that allowed authenticated non-administrative users to delete DNS zones outside their assigned scope.
Who should check
Teams running ManageEngine DDI Central 6.3.0 build 6300 and below, including those using the Windows DNS zone-scope management API.
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 version 6.3.0 build 6300 and below. The flaw is in the Windows DNS zone-scope management API, specifically the zone deletion endpoint.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-75864 (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-75864 (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 version 6.3.0 build 6300 and below. (source: https://www.manageengine.com/ca/dns-dhcp-ipam/security-updates/cve-2026-75864.html)
- The flaw is in the Windows DNS zone-scope management API, specifically the zone deletion endpoint. (source: https://www.manageengine.com/ca/dns-dhcp-ipam/security-updates/cve-2026-75864.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-75864 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75864 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-75864.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-75864
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-75864"}.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-75864
Is CVE-2026-75864 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 can delete DNS zones they are not authorized to manage, because the Windows DNS zone-scope API does not check authorization properly on the zone deletion endpoint. Deleted zones can cause DNS configuration loss, name resolution disruption, outages and loss of tenant isolation.Source: manageengine.com
Which versions are affected by CVE-2026-75864?
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 below are affected. To check, look at the build number of your DDI Central installation and compare it with 6300.Source: manageengine.com
How do I fix CVE-2026-75864?
Upgrade to a fixed version: 6301. The vendor's advisory also recommends Build 6301 or later.Source: cve.now feed data, manageengine.com