← Back
CVE-2026-35563
high
CVSS 8.5
Vulnerability in org.apache.directory.api:api-ldap-client-api (CVE-2026-35563)
Summary
vulnerability in org.apache.directory.api:api-ldap-client-api (CVE-2026-35563). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `2.1.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-35563** has been found in org.apache.directory.api:api-ldap-client-api.
Successful exploitation can lead to full system takeover. CVSS score: 8.5/10.
What to do: upgrade org.apache.directory.api:api-ldap-client-api to **2.1.8** or later.
If unsure, ask your IT team or search "org.apache.directory.api:api-ldap-client-api CVE-2026-35563" on the vendor's site.
CVE-2026-35563 (org.apache.directory.api:api-ldap-client-api) — CWE-297 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Patched: `2.1.8` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-297) exists in org.apache.directory.api:api-ldap-client-api.
📍 Affected scope
org.apache.directory.api:api-ldap-client-api — .
🔥 Severity
Severity: High (CVSS 8.5/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.1.8**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.apache.directory.api:api-ldap-client-api' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.apache.directory.api:api-ldap-client-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.directory.api:api-ldap-client-api` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.directory.api:api-ldap-client-api to 2.1.8ステージング環境で 2.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.directory.api:api-ldap-client-api
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.8"}]}]
References
- web https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nn
- web https://nvd.nist.gov/vuln/detail/CVE-2026-35563
- web http://www.openwall.com/lists/oss-security/2026/06/01/2
- web https://github.com/advisories/GHSA-85rw-g4f4-jprr
- web https://github.com/apache/directory-ldap-api/commit/57a7726d8b6436c74945c12f5ba4e12d232d2bac