CVE-2026-35563
Last modified
CVE-2026-35563 is a high-severity vulnerability rated 8.5/10 on the CVSS scale. It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. This oversight leaves the connection highly vulnerable to server impersonation and complete connection compromise. The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation. The attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store. The hostname verification has been enforced in the new version of the LDAP API
Metrics
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Directory Ldap Api | >= 2.0.0, < 2.1.7 |
References
- https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nnMailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/06/01/2Mailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-35563?
How severe is CVE-2026-35563?
How do I fix CVE-2026-35563?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-35558Improper neutralization of special elements in the authentic…7.8
- CVE-2026-35559Out-of-bounds write in the query processing components in Am…7.1
- CVE-2026-3556Philips Hue Bridge HomeKit Pair-Setup Heap-based Buffer Over…8.8
- CVE-2026-35560Improper certificate validation in the identity provider con…5.9
- CVE-2026-35561Insufficient authentication security controls in the browser…9.8
- CVE-2026-35562Allocation of resources without limits in the parsing compon…8.7
- CVE-2026-35565Stored Cross-Site Scripting (XSS) via Unsanitized Topology M…5.4
- CVE-2026-35566Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-35567Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-35568MCP Java SDK is the official Java SDK for Model Context Prot…5.7
- CVE-2026-35569ApostropheCMS is an open-source Node.js content management s…8.7
- CVE-2026-3557Philips Hue Bridge hap_pair_verify_handler Sub-TLV Parsing H…8
Are you affected by CVE-2026-35563?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
