Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
CVE-2026-129349: Apache Shiro LDAP login accepts any password after first login
CVE-2026-129349 · published 7 days ago
Summary
If you use Apache Shiro’s LDAP feature with caching turned on, a user who logs in once can later log in again with any password. This happens because the cached login bypasses the password check. Upgrade to version 3.0.1 or later, or turn off authentication caching, to stop this behavior.
What to do
- Update apache software foundation apache shiro to version 3.0.1 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Debian:12 | debian | shiro | All versions |
| Debian:13 | debian | shiro | All versions |
| Debian:14 | debian | shiro | All versions |
| – | apache software foundation | apache shiro | < 3.0.1 |
| Ubuntu:Pro:16.04:LTS | canonical | shiro | All versions |
Original advisory text
Apache Shiro: DefaultLdapRealm accepts any password when authentication caching is enabled
When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password.
A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user.
This issue affects all Apache Shiro versions through 3.0.0, only when using DefaultLdapRealm (or JndiLdapRealm) with authenticationCachingEnabled set to true, which is not the default.
Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by no longer installing AllowAllCredentialsMatcher by default.
Alternatively, disable authentication caching on the LDAP realm (this is the default), or configure a credentials matcher, such as SimpleCredentialsMatcher, that verifies credentials against the cached authentication info.
A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user.
This issue affects all Apache Shiro versions through 3.0.0, only when using DefaultLdapRealm (or JndiLdapRealm) with authenticationCachingEnabled set to true, which is not the default.
Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by no longer installing AllowAllCredentialsMatcher by default.
Alternatively, disable authentication caching on the LDAP realm (this is the default), or configure a credentials matcher, such as SimpleCredentialsMatcher, that verifies credentials against the cached authentication info.
References
- https://security-tracker.debian.org/tracker/CVE-2026-129349 Vendor Advisory
- https://lists.apache.org/thread.html/1whn52ht402lhc782c3s843c9hho8b4y
- http://www.openwall.com/lists/oss-security/2026/11/14/8
- https://ubuntu.com/security/CVE-2026-129349 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-129349 Third Party Advisory
- https://www.openwall.com/lists/oss-security/2026/11/14/8 Third Party Advisory
- https://shiro.apache.org/security-reports.html#cve_2026_129349 Third Party Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Severity
9.1
Critical
Type
CWE-287Improper Authentication
Timeline
Published15 Nov 2026
Updated22 Nov 2026
First seen14 Nov 2026
Sources
DEBIAN-CVE-2026-129349 · OSV
CVE-2026-129349 · NVD
CVE-2026-129349 · MITRE
UBUNTU-CVE-2026-129349 · OSV
Track software like this
Free during beta