CVE-2026-103878: Apache Directory LDAP API: Injection of plaintext responses during StartTLS
Apache Directory LDAP API versions before 2.1.9 can leak plaintext responses when StartTLS follows a search.
Cleartext responses during StartTLS in Apache Directory LDAP API
Apache Directory LDAP API from 2.1.0 before 2.1.9 can receive sensitive directory data in cleartext when a StartTLS extended operation is started after a Search request has already been sent, before the TLS handshake finishes. Related reporting describes this as injection of plaintext responses during that StartTLS window. An on-path attacker can therefore expose or substitute LDAP data before encryption is in place. Any application that embeds this Java client library and uses that Search-then-StartTLS sequence is affected. No public proof of concept is known, the issue is not in CISA KEV, and CVSS has not yet been scored.
What to do: Upgrade Apache Directory LDAP API to 2.1.9 and rebuild or redeploy every application that embeds 2.1.0 through versions before 2.1.9. Review LDAP client flows that issue a Search and then StartTLS, and do not treat directory data as trusted until the TLS handshake has completed.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Directory LDAP API | 2.1.0 before 2.1.9 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Cleartext transmission of sensitive information vulnerability in Apache Directory LDAP API. A StartTLS extended operation started after a Search request has been sent can lead to receive data in plain text before the TLS Handshake has been completed. This issue affects Apache Directory LDAP API: from 2.1.0 before 2.1.9. Users are recommended to upgrade to version 2.1.9, which fixes the issue.
Apache Directory LDAP API versions before 2.1.9 can leak plaintext responses when StartTLS follows a search.
Today 846 readers · 1.1K views · 848 reads · all time 159K views