With CVE-2026-129349, the Apache Shiro project has disclosed a critical flaw in the LDAP integration of its Java security framework. In a specific configuration, any password is enough to log in again as the same user after one successful login. Together with two other critical advisories published on 14 November 2026, this mainly affects Java web applications that check users against an LDAP directory or Active Directory. The flaw is fixed, and updating to the current releases is the recommended path.
What Apache Shiro is and who may be affected
Apache Shiro is an open-source framework from the Apache Software Foundation for authentication, authorization, session management and cryptography in Java applications. It is used in classic web applications, in Jakarta EE environments and together with Spring. Many enterprise applications rely on Shiro to check logins against a central directory, often via LDAP.
That is exactly where two of the three new advisories apply. Affected are applications that use DefaultLdapRealm or the older JndiLdapRealm. If you use Shiro only with a database, your own realm implementation or an external identity provider, these two LDAP issues do not affect you. The third advisory on cookies, however, covers a much larger number of installations.
CVE-2026-129349: any password after one login
According to the Shiro team’s security advisory, the problem comes from the interplay of two features. Until now, DefaultLdapRealm installed an AllowAllCredentialsMatcher by default. This component accepts any input because the actual password check is done by the LDAP directory during the so-called bind.
That works as long as every login really performs an LDAP bind. If authentication caching is enabled (authenticationCachingEnabled = true), however, Shiro stores the authentication info in a cache after a successful login. On the next login for the same user, the bind is skipped, and only the matcher that accepts everything is left. An attacker who knows a valid username can then log in as that user with any password.
The announcement on the oss-security mailing list rates the flaw at CVSS 4.0 9.1 (critical). All Shiro versions up to and including 3.0.0 are affected, but only in this combination. An important detail: authentication caching is not enabled by default in the LDAP realm. If you never switched it on, CVE-2026-129349 does not affect you. The flaw was reported by Joshua Rogers.
Why caching turns into a risk here
The case shows a familiar pattern: two features that each make sense on their own become a problem together. Caching authentication data is meant to reduce load on the directory server and speed up logins, especially in applications with heavy traffic. The permissive matcher, on the other hand, was set on the assumption that the LDAP directory checks every login itself. As soon as the cache replaces that check, the actual password verification is gone.
For developers, this is a reminder to check the assumptions behind default values before switching on optimisations such as caching. The fix targets exactly this assumption: since version 3.0.1, the LDAP realm no longer installs the permissive matcher by default.
The two other critical advisories
On the same day, the Shiro team rated two more flaws as critical:
- CVE-2026-49268 (LDAP DN injection):
DefaultLdapRealminserted the username into the DN template without escaping the special characters defined in RFC 2253. An attacker could change the structure of the distinguished name used for the LDAP bind, bypass authentication or impersonate other users. All versions up to 2.2.0 and 3.0.0-alpha-1 are affected. It is fixed in 2.2.1 and from 3.0.0-alpha-2. - CVE-2026-43828 (cookies without the Secure attribute): by default, the native session manager and the Remember-Me manager set the
JSESSIONIDandrememberMecookies without theSecureattribute, even over HTTPS. Shiro 1.0 to 2.1.0 and 3.0.0-alpha-1 are affected. It is fixed in 2.2.0 and from 3.0.0-alpha-2.
The DN injection matters most for applications that take usernames straight from login forms without validation. The missing Secure attribute increases the risk that session cookies are sent over unencrypted connections, for example when HTTP and HTTPS requests are mixed.
Which versions help now
For CVE-2026-129349, version 3.0.1 is technically enough: there, DefaultLdapRealm no longer installs AllowAllCredentialsMatcher by default. The Shiro team, however, recommends going straight to the latest release. According to the blog post, version 3.0.2 or later covers all three issues on the 3.x line, and version 2.2.1 or later covers them on the 2.x line.
The vulnerability reports page also lists further, lower-rated issues that are only fixed in 3.0.2. They include CVE-2026-74763 (medium): authorization annotations such as @RequiresRoles and @RequiresPermissions were not always enforced in certain class and interface hierarchies, for example with the shiro-guice or shiro-aspectj modules. In addition, an empty stored credential could count as a match for an empty submitted password (CVE-2026-129347, low). This is another reason to choose 3.0.2 over 3.0.1.
Keep the release policy in mind: Shiro 2 was superseded by Shiro 3 on 29 June 2026. According to the project, only the most recent release line receives all security fixes. If you still run Shiro 1.x, plan a migration.
What developers and operators should do now
- Check dependencies: search Maven or Gradle for
org.apache.shiro, including transitive dependencies of frameworks and business applications. - Update: move to 3.0.2 or later, or at least 2.2.1 on the 2.x line.
- Review the LDAP configuration: is
authenticationCachingEnabledset on the LDAP realm? If you cannot update immediately, disable caching or configure a verifying credentials matcher such asSimpleCredentialsMatcher. - Check cookies: use the browser or
curl -Ito confirm that session and Remember-Me cookies carry theSecureattribute. - Review logs: if caching was enabled, look for unusual logins, such as many sign-ins to one account from unknown networks.
The project’s advisories do not mention active exploitation. But since the root cause is publicly documented and the attack only requires a valid username, affected configurations should not stay open for long.
The Shiro flaws come in a week with several important security updates for developers. They include CVE-2026-6460 and 51 other flaws in PostgreSQL and the root-level flaw CVE-2026-129433 in Dokploy. If you run your own applications with upload or login features, our article on the Neos Flow upload flaw is another example of how framework defaults can become a risk.




