Unauthenticated LDAP metadata disclosure via omitted object filter
Published Aug 18, 2026 · Updated Aug 18, 2026
Information disclosure in authentik before 2026.2.6 and 2026.5.5 allows remote attackers to read LDAP metadata via the debug API. The LDAPSourceViewSet.debug action in authentik/sources/ldap/api.py was exposed without the ObjectFilter backend used elsewhere in the LDAP Source API, so object-level read authorization on the source was skipped before the server queried the upstream directory with its configured bind credentials. Reachability requires network access to an authentik deployment with a configured LDAP Source; the response is limited to distinguished names and attribute names, exposing directory structure, naming conventions, and the existence of specific accounts and groups, but not attribute values.
Summary
What happened
Information disclosure in authentik before 2026.2.6 and 2026.5.5 allows remote attackers to read LDAP metadata via the debug API. The LDAPSourceViewSet.debug action in authentik/sources/ldap/api.py was exposed without the ObjectFilter backend used elsewhere in the LDAP Source API, so object-level read authorization on the source was skipped before the server queried the upstream directory with its configured bind credentials. Reachability requires network access to an authentik deployment with a configured LDAP Source; the response is limited to distinguished names and attribute names, exposing directory structure, naming conventions, and the existence of specific accounts and groups, but not attribute values.
The record
- CVE
- CVE-2026-55106
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Authentik Security
- Product
- authentik
- Classifications
- CWE-862, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2026.2.6
- Affected versionversion=>= 2026.5.0, < 2026.5.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo