CVE-2026-35563
LDAP client 2.1.7 omits hostname verification, enabling MITM.
Is CVE-2026-35563 being exploited?
Not confirmed. CVE-2026-35563 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-35563?
CVE-2026-35563 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-35563?
Yes. A fix has been recorded for CVE-2026-35563. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-35563 affect?
CVE-2026-35563 affects LDAP client 2.1.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-35563?
Upgrade to a version with hostname verification
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM with trusted cert enables LDAP server impersonation, risking data exposure and potential client-side code execution.
Patch when possible
- affected>= 2.0.0 and <= 2.1.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.