CVE-2026-90979

LDAPCache and LDAPBackingEngine build LDAP search filters for user lookup and role lookup by textually substituting the placeholders %u, %dn, and %fqdn (drawn from the login name, the resolved user DN, and its fully qualified namespace form) into administrator-configured filter templates (userFilter, roleFilter). Before the fix, the only sanitization applied to the substituted value was double backslashed: filter = filter.replaceAll(Pattern.quote("%u"), Matcher.quoteReplacement(user)); filter = filter.replace("\\", "\\\\"); This does not escape the other characters RFC 4515 requires escaping in an LDAP search filter: *, (, ), and NUL. A login name containing any of these can change the structure of the resulting filter rather than being matched as a literal value (e.g. a crafted username can turn an equality match into a wildcard match, or close/reopen filter clauses), widening what the search returns and potentially causing a login or role lookup to match an LDAP entry other than the intended one, over-granting roles, and depending on deployment-specific filter templates, potentially affecting which account a login resolved to. It's not exploitable through every entry points: LDAPLoginModule and LDAPPubkeyLoginModule both called Util.doRFC2254Encoding() (correct RFC 4515 escaping) on the login name before handing it to LDAPCache, which masked the missing escaping in LDAPCache for those two call paths. Using LDAPCache directly (bypassing the login modules) does not reproduce through the normal LDAPLoginModule/LDAPPubkeyLoginModule authentication flow for this reason. It does reproduce through two other call paths that reach LDAPCache/LDAPBackingEngine without any prior escaping: * GSSAPILdapLoginModule passes the NameCallback name straight through, unescaped. * LDAPBackingEngine (listRoles) passes principal.getName() straight through, unescaped.

• CWE-90

• https://karaf.apache.org/security/cve-2026-90979.txtVendor Advisory
• https://www.openwall.com/lists/oss-security/2026/09/28/2Mailing List, Third Party Advisory

Published

Sep 28, 2026

Last Modified

Oct 8, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-90972The WP Fusion Lite WordPress plugin before 3.48.0 does not …5.4
• CVE-2026-90974The WP Fusion Lite WordPress plugin before 3.48.0 does not …6.5
• CVE-2026-90975A vulnerability in Realtek's RtUsbA64.sys USB audio driver a…7.8
• CVE-2026-90976The Clean Login WordPress plugin before 1.19 does not check …5.3
• CVE-2026-90977The Clean Login WordPress plugin before 1.19 does not verify…5.3
• CVE-2026-90978The Filter Gallery WordPress plugin before 1.1.5 does not ve…7.1
• CVE-2026-9098In Casdoor versions 2.362.0 and earlier, the SAML callback h…9.1
• CVE-2026-90981The Newsletter – Send awesome emails from WordPress plugin f…6.1
• CVE-2026-90982@fastify/static is a Fastify plugin that serves static files…5.3
• CVE-2026-90983Use of Client-Side authentication vulnerability in Hayat Hea…8.2
• CVE-2026-90984The Generate PDF using Contact Form 7 WordPress plugin befor…5.8
• CVE-2026-90985The WPC Smart Compare for WooCommerce WordPress plugin befor…5.3