---
id: CVE-2026-90979
title: "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 f…"
summary: "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 f…"
severity: none
cwe:
  - CWE-90
vendor: Apache Software Foundation
product: org.apache.karaf.jaas.modules.ldap
affected:
  - org.apache.karaf.jaas.modules.ldap < 4.4.12
published: '2026-09-28'
updated: '2026-09-28'
sourceUpdated: '2026-09-28T10:16:45.990'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-90979'
references:
  - url: 'https://karaf.apache.org/security/cve-2026-90979.txt'
    label: security@apache.org
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-28T10:07:17.786Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.