CVE Index中文
L3 · ShartedApache Shiro · Java · LDAP · authenticationapache-shiro-november

Apache Shiro discloses LDAP login and authorization bypasses

Apache disclosed eight Shiro flaws. With LDAP authentication caching enabled, an attacker who knows a previously authenticated username can log in with any password. Other flaws affect authorization annotations, session handling and optional integrations. Upgrade to 3.0.2 or later.

Disclosed
Nov 13, 2026
Public disclosure date
Severity
CVSS 9.1 × 1
8 CVEs tracked here
Splash zone
Shiro apps with LDAP auth caching, affected authorization annotations, or one of the other configurations listed below.
java
In the wild
Unknown

What happened

CVE-2026-129349 requires an application to enable LDAP authentication caching and the target user to authenticate successfully first. Subsequent cache hits skip the LDAP bind. The default matcher on the affected realm accepts the submitted password without verifying it. Apache rates the bypass 9.1 under CVSS 4.0. The advisories do not report attacks in the wild.

Shiro 3.0.1 first fixed the LDAP and remember-me issues. The other six fixes require 3.0.2. Apache’s open-source security support follows the newest release line, so applications still running 1.x or 2.x need a migration plan. The current batch is L3 because it affects a widely used authentication library and the critical bypass depends on specific configuration and a cached login.

What’s in the bowl

LDAP authentication cache bypass

In Shiro through 3.0.0, a known username with cached authentication can log in with any password when DefaultLdapRealm or JndiLdapRealm uses authentication caching and the permissive default matcher.

Authorization annotations skipped

Through 3.0.1, interface annotations can be skipped in Guice, AspectJ, CDI and Jakarta EE integrations. Class and superclass annotations can also be skipped with Guice or AspectJ. The affected CDI and Jakarta EE modules start at 2.0.0-alpha-0.

Case-sensitive filter matching

In 3.0.1, a manually created ShiroFilterFactoryBean can miss protected static paths on a case-insensitive filesystem. The Shiro Spring starter-created bean is outside this case.

Empty password matches an empty credential

Through 3.0.1, DefaultPasswordService and SimpleCredentialsMatcher can authenticate an empty submitted password for an account with an empty stored credential.

Unescaped principal tag output

Through 3.0.1, applications using the Jakarta Pages or Jakarta Faces principal tag can render script from an untrusted principal value. The affected Jakarta Faces module starts at 2.0.0-alpha-0.

Stale file-backed realm permissions

Through 3.0.1, reloading a file-backed PropertiesRealm can leave deleted users and previous permissions in effect.

Unsafe saved-form replay

From 2.0.0-alpha-0 through 3.0.1, Jakarta EE integration with form saving enabled (the default) can weaken cookie attributes or send replayed form data and cookies to an untrusted host.

Remember-me session fixation

Through 3.0.0, restoring a remembered user can retain the session ID and accept URL session IDs even with URL rewriting disabled. Remember-me must be enabled.

Fixed versions

ProductSafe fromNote
Apache Shiro 3.x3.0.2Covers all eight disclosures
Apache Shiro 1.x and 2.xNo fixSuperseded upstream

Crime-scene timeline

  1. Nov 8, 2026

    Apache announces Shiro 3.0.2

  2. Nov 13, 23:28 UTC

    First bulletin carries the static-path filter advisory

  3. Nov 14, 2026

    The other seven advisories follow on the mailing list

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.