A remote attacker can inject LDAP special characters into the Distinguished Name (DN) construction in DefaultLdapRealm class. User-supplied username input is directly concatenated into the LDAP DN template without any escaping of RFC 2253 special characters. This allows an attacker to manipulate the DN structure used for LDAP bind authentication, potentially bypassing authentication or impersonating other users.
This issue affects all Apache Shiro versions through 2.2.0, and 3.0.0-alpha-1 when usingĀ DefaultLdapRealm
Upgrade to Apache Shiro 2.2.1 or 3.0.0-alpha-2 or later, which fixes the issue.
References
| Link | Resource |
|---|---|
| https://lists.apache.org/thread/svszql3od8td7hn6conyj2oq70v53b5s | Mailing List Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2026/06/17/8 | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
18 Jun 2026, 14:45
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-06-17 14:17
Updated : 2026-06-18 14:45
NVD link : CVE-2026-49268
Mitre link : CVE-2026-49268
CVE.ORG link : CVE-2026-49268
JSON object : View
Products Affected
apache
- shiro
CWE
CWE-90
Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')
