Apache Shiro DefaultLdapRealm accepts any password after cached login
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-287.
Summary
Apache Shiro through 3.0.0 is affected when DefaultLdapRealm or JndiLdapRealm has authentication caching enabled, which is not the default. After one successful login, later logins for that user accept any password, because cached authentication skips the LDAP bind and the default AllowAllCredentialsMatcher accepts all credentials. A remote attacker who knows a valid username can log in as that user without authentication.
Written with Claude Haiku 5.5 from the sources below · 2026-11-15
Description from the CNA
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade Apache Shiro to version 3.0.1 or later, which no longer installs AllowAllCredentialsMatcher by default. Alternatively, keep authentication caching disabled on DefaultLdapRealm (the default), or configure a credentials matcher such as SimpleCredentialsMatcher.
Written with Claude Haiku 5.5 from the sources below · 2026-11-15
- Fix · CNA Apache Shiro (Apache Software Foundation) Fixed in 3.0.1
Timeline
- 2026-11-15 Threatist record created from CVE-2026-129349
- 2026-11-15 Alias added: GHSA-3j37-vw7v-fxxw
References
More Apache vulnerabilities
- TI-2025-18529 Path equivalence in Apache Tomcat allows code execution via PUT KEVCVSS 3.1CRITICAL 10.0
- TI-2024-30292 Forced browsing in Apache OFBiz bypasses controller-view authorization KEVCVSS 3.1CRITICAL 9.8
- TI-2024-26062 Incorrect authorization in Apache OFBiz exposes screen rendering code KEVCVSS 3.1CRITICAL 9.8
- TI-2024-21190 Path traversal in Apache OFBiz leads to remote code execution KEVCVSS 3.1CRITICAL 9.8
- TI-2024-18186 Remote command execution in Apache HugeGraph-Server via Gremlin KEVCVSS 3.1CRITICAL 9.8
- TI-2023-25106 Apache ActiveMQ OpenWire deserialization allows remote code execution KEVCVSS 3.1CRITICAL 10.0
Sources
- CVE-2026-129349 · CVE Program
- CVE-2026-129349 · NVD
- FIRST EPSS
- GHSA-3j37-vw7v-fxxw · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences