CVE-2026-35563: Apache Directory LDAP API · Improper Validation of Certificate with Host Mismatch
Affects Apache Directory LDAP APISource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 1 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Directory LDAP API | Affected
| Fixed in– |
MavenApache Software Foundation/org.apache.directory.api:api-ldap-client-apipkg:maven/Apache Software Foundation/org.apache.directory.api:api-ldap-client-apiOther threats | Affected
| Fixed in– |
Mavenorg.apache.directory.api/api-ldap-clientpkg:maven/org.apache.directory.api/api-ldap-clientOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed by enforcing hostname verification in newer versions of the Apache Directory LDAP API. Users should upgrade to a version that includes this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
Description
Apache Directory LDAP API version 2.0.0 contains a vulnerability where the LDAP client does not verify that the server certificate matches the intended LDAP hostname. Although the certificate chain is validated against trusted authorities, the lack of endpoint identification allows acceptance of valid certificates issued for unrelated hosts. This flaw enables potential server impersonation and connection compromise if an attacker can perform a man-in-the-middle attack with a trusted certificate. Hostname verification has been enforced in newer versions of the LDAP API.