Answer in brief
CVE-2026-129349 records a Critical severity (CVSS 9.1) vulnerability in Apache Shiro: DefaultLdapRealm accepts any password when authentication caching is enabled. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/org.apache.shiro:shiro-core (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/org.apache.shiro:shiro-core (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/org.apache.shiro:shiro-coregeneric | >=0 <3.0.1 | 3.0.1 |
Published upstream
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 15, 2026
When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password. A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user. This issue affects all Apache Shiro versions through 3.0.0, only when using DefaultLdapRealm (or JndiLdapRealm) with authenticationCachingEnabled set to true, which is not the default. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by no longer installing AllowAllCredentialsMatcher by default. Alternatively, disable authentication caching on the LDAP realm (this is the default), or configure a credentials matcher, such as SimpleCredentialsMatcher, that verifies credentials against the cached authentication info.
Quoted source text, attributed separately from HOL analysis.