dbcve.org
Directory Ldap ApiApplication · Apache

CVE-2026-35563

HIGH · 8.5 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to 2.1.7 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LDAP client in version 2.1.7 validates the certificate chain against trusted authorities but fails to verify that the server certificate matches the intended LDAP hostname. This allows a MITM attacker with a trusted certificate for an unrelated host to impersonate the LDAP server and compromise the connection.

MitigationUpgrade to the newer version of the LDAP API that enforces hostname verification, then verify LDAP connectivity continues to function correctly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Directory Ldap ApiApplication
Affected:>= 2.0.0, < 2.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Directory Ldap Api library usage
    Locate the ldap-api library in your deployment: check for JAR files named ldap-api-*.jar, or inspect Maven/Gradle dependency files (pom.xml, build.gradle) for the Apache Directory Ldap Api artifact
    Affected if The library version is 2.0.0 or higher but below 2.1.7
  2. Verify SSL/TLS is enabled for LDAP connections
    Inspect your application configuration or connection code for LDAPS (ldaps:// URL scheme) or StartTLS usage. Check if javax.net.ssl properties or custom SSLContext are configured for LDAP connections
    Affected if LDAP connections use SSL or TLS encryption (the vulnerability requires a secure channel to be established)
  3. Confirm hostname verification is not enforced
    Review the LDAP connection code or SSL configuration for any custom TrustManager,HostnameVerifier, or disabled verification flags. Look for patterns like DisabledCertificateVerification, TrustAllSSLVerifier, or similar configurations that bypass hostname validation
    Affected if Hostname verification is explicitly disabled or a TrustManager that does not validate endpoint identity is in use

You are affected if Apache Directory Ldap Api version 2.0.0 to < 2.1.7 is in use AND your application connects to LDAP servers over SSL/TLS with hostname verification disabled or missing

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.7 or later
Fixed in 2.1.7
Interim mitigation

Upgrade to the newer version of the LDAP API that enforces hostname verification, then verify LDAP connectivity continues to function correctly.

Recommended fix High confidence

2.1.8 or later

  1. 1. Identify all applications and services using Directory Ldap Api version 2.0.0 through 2.1.6
  2. 2. Upgrade the Directory Ldap Api dependency to version 2.1.8 or later
  3. 3. Rebuild and redeploy all affected applications
  4. 4. Verify LDAPS connections are working after the upgrade
  5. 5. Test that hostname verification is functioning correctly (certificate must match the LDAP server hostname)
Caveat Minor - upgrade is backward compatible; only adds missing security validation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Directory Ldap Api Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35563 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35563 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data