Low Severity CVE-2026-129349
Published: Nov 17, 2026

[GitHub] CVE-2026-129349

Other
Type
N/A
CVSS Score
6
Views
Anonymous
Author

Description

Apache Shiro <=3.0.0 DefaultLdapRealm + authenticationCachingEnabled: one valid login, then ANY password (incl. empty) authenticates — cached auth skips the LDAP bind and AllowAllCredentialsMatcher accepts everything. Real realm + real in-memory LDAP; only diff is shiro 3.0.0 vs fixed 3.0.1.

# CVE-2026-129349 — Apache Shiro `DefaultLdapRealm` accepts any password after one successful login when authentication caching is enabled

[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![Research status: validated](https://img.shields.io/badge/research-validated%20differential-success.svg)](#5-expected-results)

| | |
| --- | --- |
| **CVE** | CVE-2026-129349 |
| **Component** | Apache Shiro `DefaultLdapRealm` (also `JndiLdapRealm`), `core/src/main/java/org/apache/shiro/realm/ldap/DefaultLdapRealm.java` |
| **Affected** | all Apache Shiro versions through 3.0.0, **only** with `DefaultLdapRealm`/`JndiLdapRealm` and `authenticationCachingEnabled = true` (not the default) |
| **Fixed in** | 3.0.1 — `DefaultLdapRealm`'s constructor no longer installs `AllowAllCredentialsMatcher` by default |
| **CWE** | CWE-287 (Improper Authentication), CWE-613 (Insufficient Session Expiration analog: stale cached authentication) |
| **Impact** | Authentication bypass: an attacker who knows (or guesses) any valid username can authenticate as that user with an arbitrary password — including the empty string — after that user has logged in once |
| **Vector** | Any authentication path backed by the affected realm configuration; network position is whatever reaches the application |
| **Trigger** | one valid login primes the authentication cache; every subsequent `UsernamePasswordToken` for the same user is accepted without an LDAP bind because the cached `AuthenticationInfo` is matched by `AllowAllCredentialsMatcher` |
| **Credit** | Apache Shiro security announcement (ASF thread `1whn52ht402lhc782c3s843c9hho8b4y`) |

Apache Shiro's `DefaultLdapRealm` historically installed
`AllowAllCredentialsMatcher` in its constructor — "credentials matching is
not necessary, the LDAP directory will do it automatically". That
reasoning holds only while every authentication performs an LDAP bind.
When `authenticationCachingEnabled = true`, a cached authentication skips

Community Rating
0

Login to rate this exploit

Quick Actions