Apache Shiro (14 Nov): three advisories rated Critical by the Shiro team — any password accepted with LDAP authentication caching, LDAP DN injection in DefaultLdapRealm, and session cookies without the Secure attribute
The Apache Shiro team said in a blog post published 14 November 2026 that it has published three critical security advisories, two affecting DefaultLdapRealm and one the default cookie settings (source: Apache Shiro). CVE-2026-129349: when authentication caching is enabled on DefaultLdapRealm (or JndiLdapRealm), a user who has logged in once can log in again with any password, because a cached authentication skips the LDAP bind and the default AllowAllCredentialsMatcher accepts any credentials; Shiro says this is not the default setting (source: Apache Shiro).
CVE-2026-49268: a remote attacker can inject LDAP special characters into the DN built by DefaultLdapRealm, which Shiro says can bypass authentication or impersonate other users (source: Apache Shiro). CVE-2026-43828: by default the Shiro-native session manager and Remember-Me manager sent the JSESSIONID and rememberMe cookies without the Secure attribute, even over HTTPS (source: Apache Shiro).
The post gives no CVSS scores and does not report exploitation.
- Product
- Apache Shiro (Java security framework)
- Versions
- Per Apache Shiro: CVE-2026-129349 affects all Shiro versions through 3.0.0, only with DefaultLdapRealm (or JndiLdapRealm) and authenticationCachingEnabled set to true, fixed in 3.0.1; CVE-2026-49268 affects all versions through 2.2.0 and 3.0.0-alpha-1 when using DefaultLdapRealm, fixed in 2.2.1 or 3.0.0-alpha-2; CVE-2026-43828 affects Shiro 1.0 to 2.1.0 and 3.0.0-alpha-1, fixed in 2.2.0 or 3.0.0-alpha-2 (as of 19 Nov).
- CVSS
- Not given in the Shiro post; Shiro rates all three Critical
- Exploited in Australia?
- unknown
- Patch to
- Per Apache Shiro: "Version 3.0.2 or later covers all three issues on the 3.x line, and 2.2.1 or later covers them on the 2.x line." Workaround for CVE-2026-129349: keep authentication caching disabled on the LDAP realm (the default), or configure a credentials matcher such as SimpleCredentialsMatcher.
