CVE
Zoho DDI Central authenticated command injection in clear_blocked_domains
- Exploited
- No known exploitation
- Fix
- Fixed in 6500
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Windows DDI Agent DDI Central build 6301 or below (6.3.1)
Summary
Zohocorp ManageEngine DDI Central builds before the fixed release contain an authenticated command injection flaw in the Windows DDI Agent's clear_blocked_domains function. An attacker with high-privilege login credentials can reach it over the network and use specially crafted blocked-domain values to run arbitrary commands on Windows systems.
Original description
Zohocorp Manageengine DDI Central build below 6500 are affected by a authenticated command injection vulnerability in the Windows DDI Agent's clear_blocked_domains functionality, allowing specially crafted blocked-domain values to trigger arbitrary command execution on Windows systems.
Who should check
Teams running ManageEngine DDI Central build 6301 or below with Windows DDI Agents
“DDI Central 6.3.1 / Build 6301 and below”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Windows DDI Agent DDI Central build 6301 or below (6.3.1)Upgrade to a fixed version: 6500.
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-95645 (Authenticated Command Injection), 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-95645 (entry last updated 2026-11-18):
Affected:
- Zohocorp DDI Central: fixed in 6500
Fixed versions: 6500.
Conditions (all must be true for the bug to be hit):
- Windows DDI Agent (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-95645.html)
- DDI Central build 6301 or below (6.3.1) (source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/cve-2026-95645.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-95645 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95645 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-95645.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-95645
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-95645"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Zohocorp DDI Central
fixed in 6500
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-95645 |
| Record | NVD · CVE-2026-95645 |
| Other links 1 | |
| Link | manageengine.com · dns-dhcp-ipam/security-updates/cve-2026-95645.html |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-95645
Is CVE-2026-95645 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?
The Windows DDI Agent's blocked-domain management feature does not properly handle input, so an authenticated user can inject operating system commands. Injected commands could run with the privileges available to the DDI Agent process.Source: manageengine.com
Which versions are affected by CVE-2026-95645?
DDI Central: before 6500.Source: cve.now feed data
Am I affected, and how do I check?
DDI Central build 6301 and below (6.3.1) are listed as affected. To check a installation, look at the DDI Central build number and whether the Windows DDI Agent is in use.Source: manageengine.com
How do I fix CVE-2026-95645?
Upgrade to a fixed version: 6500. The vendor's advisory also recommends Build 6500 or later.Source: cve.now feed data, manageengine.com