# Apache Directory LDAP API lacks server certificate verification for LDAP hostnames

Advisory record · `GHSA-85rw-g4f4-jprr`

- **Identifiers:** `GHSA-85rw-g4f4-jprr` · `CVE-2026-35563`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-297](https://cwe.mitre.org/data/definitions/297.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 1 Jun 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Jun 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.directory.api:api-ldap-client-api` (Maven): affected `>=2.0.0, <2.1.8`; fixed in `2.1.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Directory LDAP API (api-ldap-client-api, Maven) versions 2.0.0 up to 2.1.8 do not verify that the server certificate matches the LDAP hostname the client connects to. An attacker with man-in-the-middle access to the network who can present a certificate trusted by the client's trust store can impersonate the server and compromise the connection. Upgrade to version 2.1.8, which enforces hostname verification.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 4.0: `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`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-85rw-g4f4-jprr)

## Sources

- [GitHub Advisory Database: GHSA-85rw-g4f4-jprr](https://github.com/advisories/GHSA-85rw-g4f4-jprr)
- [OSV: GHSA-85rw-g4f4-jprr](https://osv.dev/vulnerability/GHSA-85rw-g4f4-jprr)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-35563>
- <https://github.com/apache/directory-ldap-api/commit/57a7726d8b6436c74945c12f5ba4e12d232d2bac>
- <https://github.com/apache/directory-ldap-api>
- <https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nn>
- <http://www.openwall.com/lists/oss-security/2026/06/01/2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-85rw-g4f4-jprr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-85rw-g4f4-jprr/>. Everything for agents: <https://agentprime.io/llms.txt>.