Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

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

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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

Check the vendor advisory for the affected versions of 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.directory.api:api-ldap-client-api を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.directory.api:api-ldap-client-api to 2.1.8

    ステージング環境で 2.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.directory.api:api-ldap-client-api
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.1.8"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details