---
title: Apache Shiro CVE-2026-129349: with LDAP authentication caching on, anyone who knows a username can log in with any password after that user's first login | ctxsec
url: https://ctxsec.com/items/apache-shiro-cve-2026-129349-defaultldaprealm-auth-caching-accepts-any-password-fixed-3-0-1
description: "Apache Shiro says that when authentication caching is enabled on DefaultLdapRealm (or JndiLdapRealm), a cached login skips the LDAP bind, and the AllowAllCredentialsMatcher the realm installs by default then accepts any credentials. After a user has logged in once, an attacker who knows the username can authenticate as them with any password. All Shiro versions through 3.0.0 are affected, but only with authenticationCachingEnabled set to true, which is not the default. CVSS 4.0 is 9.1. Fixed in 3.0.1, which no longer installs AllowAllCredentialsMatcher by default."
status: "official (Apache Shiro advisory via oss-security, Nov 14, 2026; CVE record); fixed in 3.0.1; no exploitation reported"
published: 2026-11-15
---

> Apache Shiro says that when authentication caching is enabled on DefaultLdapRealm (or JndiLdapRealm), a cached login skips the LDAP bind, and the AllowAllCredentialsMatcher the realm installs by default then accepts any credentials. After a user has logged in once, an attacker who knows the username can authenticate as them with any password. All Shiro versions through 3.0.0 are affected, but only with authenticationCachingEnabled set to true, which is not the default. CVSS 4.0 is 9.1. Fixed in 3.0.1, which no longer installs AllowAllCredentialsMatcher by default.

[← Cybersecurity News](/news) · [markdown](/items/apache-shiro-cve-2026-129349-defaultldaprealm-auth-caching-accepts-any-password-fixed-3-0-1.md)

official (Apache Shiro advisory via oss-security, Nov 14, 2026; CVE record); fixed in 3.0.1; no exploitation reported

2026-11-15 3:36 PM ET

### Apache Shiro CVE-2026-129349: with LDAP authentication caching on, anyone who knows a username can log in with any password after that user's first login

- **Check:** search your Shiro config (shiro.ini, Spring beans) for `DefaultLdapRealm` or `JndiLdapRealm` with `authenticationCachingEnabled = true`. Remember Shiro is often bundled inside other Java products, so check vendor apps too.
- **Fix:** upgrade to Shiro 3.0.1, or turn authentication caching off on the LDAP realm, or set a credentials matcher such as SimpleCredentialsMatcher that checks against the cached info.
- **Look back:** for affected apps, review logins that succeeded after earlier failed attempts for the same user, or from unusual sources, since a cached account would have accepted wrong passwords.

Sources: [oss-security: CVE-2026-129349 Apache Shiro DefaultLdapRealm accepts any password when authentication caching is enabled (Nov 14, 2026)](http://www.openwall.com/lists/oss-security/2026/11/14/8) · [Apache Shiro announcement (lists.apache.org)](https://lists.apache.org/thread.html/1whn52ht402lhc782c3s843c9hho8b4y) · [GitHub Advisory GHSA-3j37-vw7v-fxxw (CVE-2026-129349)](https://github.com/advisories/GHSA-3j37-vw7v-fxxw)
