Skip to content
TrustList
Security advisories

Apache Shiro flaw let cached LDAP logins accept any password

Editorial

By TrustList Editorial

CVE-2026-129349 is critical where DefaultLdapRealm runs with authentication caching on; 3.0.1 fixes it with several other flaws, and 3.0.2 fixes four low-severity issues found since.

About Apache Shiro flaw let cached LDAP logins accept any password

Apache Shiro flaw let cached LDAP logins accept any password

16 November 2026: Apache Shiro, the Java security framework, has fixed CVE-2026-129349, a critical flaw that lets an attacker who knows a valid username log in as that user with any password, once the real user has signed in successfully. It affects every version up to 3.0.0, but only applications that use DefaultLdapRealm or JndiLdapRealm with authenticationCachingEnabled set to true, which is not the default. Version 3.0.1 fixes it.

Not yet independently verified. The Apache Shiro security page gives no publication date for these entries; the date is that of Belgium's Centre for Cybersecurity warning, which scores CVE-2026-129349 at 9.1 on CVSS 4.0. We will update this when it can be confirmed, and remove this note.

Why the cache skipped the password check

The realm checks a password by binding to the LDAP directory. Once a login is cached, that bind is skipped, and the credentials matcher DefaultLdapRealm installed by default, AllowAllCredentialsMatcher, accepted whatever was offered. Shiro 3.0.1 no longer installs that matcher by default.

Where an upgrade has to wait, the project gives two workarounds: turn authentication caching off on the LDAP realm, which is the default setting, or set a credentials matcher such as SimpleCredentialsMatcher that checks the password against the cached information. Belgium's Centre for Cybersecurity scores the flaw 9.1 on CVSS 4.0 and told Shiro users on 16 November to patch with the highest priority. Joshua Rogers reported it.

More fixes in 3.0.1, four in 3.0.2

The project's security page lists the other flaws fixed by 3.0.1, among them:

  • CVE-2026-74762, medium: session fixation when a user is restored from a "Remember me" cookie, and session IDs accepted from the URL even with URL rewriting off;
  • CVE-2026-58301 and CVE-2026-88019, both in the Jakarta EE integration module: a request that makes the server connect to an attacker's URL, and form resubmission after login that can drop cookie security attributes and send data to an untrusted host.

A later release, 3.0.2, fixes four low-severity issues in 3.0.1 and earlier: an incomplete case-sensitivity fix in a manually created ShiroFilterFactoryBean (CVE-2026-114737), empty stored passwords matching an empty submitted one (CVE-2026-129347), unescaped output in the shiro:principal tags (CVE-2026-129320), and removed users that stay active after PropertiesRealm reloads its file (CVE-2026-129348).

Finding Shiro in your estate

Shiro is often a transitive dependency, pulled in by an application framework or a vendor product rather than chosen directly, so a dependency scan is the quickest way to see where it runs. Only the newest release line gets every security fix, the project says; older lines need commercial support.

The LDAP flaw matters most for internal portals and admin consoles that sign staff in against Active Directory or another LDAP directory.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in