CVE-2026-23906: Apache Druid · Improper Authentication
Affects Apache DruidSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 36.0.0 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 36.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade Apache Druid to 36.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Druid | Affected
| Fixed in
|
AI-suggested
1. Immediately disable anonymous bind capabilities on the LDAP servers used for Apache Druid authentication. This is the most effective short-term mitigation and does not require upgrading Druid. 2. Upgrade Apache Druid to version 36.0.0 or later as soon as possible, which includes a fix that properly rejects anonymous LDAP bind attempts and enforces correct authentication validation. 3. Audit LDAP server configurations regularly to ensure anonymous binds remain disabled and review access logs for suspicious bind attempts. 4. Implement network segmentation and access controls to limit exposure of the Druid cluster and LDAP servers to only trusted internal networks or VPNs. 5. Monitor Druid logs and query activity for unusual patterns that may indicate exploitation attempts or unauthorized access. 6. Employ multi-factor authentication (MFA) where possible on administrative interfaces to reduce risk if credentials are compromised. 7. Conduct security awareness and incident response drills focused on detecting and responding to authentication bypass scenarios. 8. Review and tighten role-based access controls within Druid to minimize privileges granted to users, limiting potential damage from compromised accounts.
Description
Affected Products and Versions * Apache Druid * Affected Versions: 0.17.0 through 35.x (all versions prior to 36.0.0) * Prerequisites: * druid-basic-security extension enabled * LDAP authenticator configured * Underlying LDAP server permits anonymous bind Vulnerability Description An authentication bypass vulnerability exists in Apache Druid when using the druid-basic-security extension with LDAP authentication. If the underlying LDAP server is configured to allow anonymous binds, an attacker can bypass authentication by providing an existing username with an empty password. This allows unauthorized access to otherwise restricted Druid resources without valid credentials. The vulnerability stems from improper validation of LDAP authentication responses when anonymous binds are permitted, effectively treating anonymous bind success as valid user authentication. Impact A remote, unauthenticated attacker can: * Gain unauthorized access to the Apache Druid cluster * Access sensitive data stored in Druid datasources * Execute queries and potentially manipulate data * Access administrative interfaces if the bypassed account has elevated privileges * Completely compromise the confidentiality, integrity, and availability of the Druid deployment Mitigation Immediate Mitigation (No Druid Upgrade Required): * Disable anonymous bind on your LDAP server. This prevents the vulnerability from being exploitable and is the recommended immediate action. Resolution * Upgrade Apache Druid to version 36.0.0 or later, which includes fixes to properly reject anonymous LDAP bind attempts.