Apache Druid fixed an authentication bypass in its druid-basic-security extension when Druid is configured to authenticate against LDAP and the backing LDAP server permits anonymous binds. Under this configuration, an attacker can supply a valid username with an empty password and be incorrectly treated as authenticated because Druid misinterprets an “anonymous bind success” response as proof of successful user authentication (CVE-2026-23906). The issue is rated “Important” severity by the Apache Software Foundation and enables remote, unauthenticated access to Druid clusters.
Successful exploitation allows an attacker to inherit the permissions of the impersonated account, potentially enabling access to sensitive data in Druid datasources, execution of queries, data manipulation, and access to administrative interfaces if a privileged user is targeted. Affected versions are reported as 0.17.0 through 35.x (all versions prior to 36.0.0) when the LDAP authenticator is in use; immediate mitigation is to disable LDAP anonymous bind on the directory server, and organizations should apply the vendor’s security update/upgrade to a fixed release.

See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
The Apache Software Foundation released Apache Druid 36.0.0 to fix CVE-2026-23906, an authentication bypass affecting deployments using druid-basic-security with LDAP authentication and LDAP servers that allow anonymous binds. The flaw affects Druid versions 0.17.0 through all 35.x releases, and administrators were advised to disable anonymous bind as a workaround if they could not upgrade immediately.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.