Loading vulnerability…
CVE-2026-35563 affects the Apache Directory LDAP API LDAP client implementation, reported as affecting org.apache.directory.api:api-ldap-client-api versions 2.0.0 through 2.1.7, with version 2.1.7 explicitly described as vulnerable. The flaw is caused by incomplete TLS server identity verification: the client validates the presented certificate chain against a trusted authority but does not verify that the server certificate matches the intended LDAP hostname. As a result, a certificate that is otherwise valid and trusted, but issued for a different host, can be accepted during LDAPS/TLS connection establishment. This breaks endpoint identification and enables LDAP server impersonation in a man-in-the-middle scenario.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.