CVE-2026-44617
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk29th percentile - higher than 29% of all known CVEs
Summary
Apache Zeppelin versions 0.11.1, 0.11.2, and 0.12.0 are vulnerable to LDAP filter injection. LdapRealm uses incorrect escaping (RFC 4514 instead of RFC 4515), leaving filter characters insufficiently escaped. This is an incomplete fix of CVE-2024-31867.
Risk Assessment
An attacker can inject special characters into LDAP filters, potentially leading to unauthorized access to directory data.
Recommendation
It is recommended to upgrade Apache Zeppelin to version 0.12.1, which fixes the issue.
Other vulnerabilities in Apache Zeppelin
See all- CVE-2026-44615Medium
In Apache Zeppelin versions 0.9.0 through 0.12.0, when FileSystemNotebookRepo is configured, an authenticated attacker with rename or folder operation permissions can use traversal segments in note or folder paths. Zeppelin composes these into filesystem paths without ensuring they remain under the configured notebook directory, potentially allowing file move, write, or delete outside the notebook root.
- CVE-2026-44616Medium
Apache Zeppelin versions 0.6.0 through 0.12.0 are vulnerable to LDAP injection. ActiveDirectoryGroupRealm constructs LDAP filters without escaping user input, allowing an authenticated attacker to inject filter syntax via the user-search endpoint.
- CVE-2026-44613Medium
Apache Zeppelin versions 0.6.0 through 0.12.0 are vulnerable to Cross-Site Request Forgery (CSRF). The default CORS configuration allows cross-origin state-changing requests and accepts text/plain bodies, enabling an attacker to perform actions on behalf of an authenticated user.
Original NVD description (English source)
LDAP filter injection vulnerability in Apache Zeppelin. LdapRealm used RFC 4514 distinguished-name escaping when constructing LDAP search filters instead of RFC 4515 filter escaping, leaving special filter characters insufficiently escaped. This is an incomplete fix of CVE-2024-31867. This issue affects Apache Zeppelin versions 0.11.1, 0.11.2, and 0.12.0. Users are recommended to upgrade to version 0.12.1, which fixes this issue.