Improper Authentication Affecting shiro package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.6% (49th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN14-SHIRO-22550288
  • published15 Nov 2026
  • disclosed15 Nov 2026

Introduced: 15 Nov 2026

NewCVE-2026-129349  (opens in a new tab)
CWE-287  (opens in a new tab)

How to fix?

There is no fixed version for Debian:14 shiro.

NVD Description

Note: Versions mentioned in the description apply only to the upstream shiro package and not the shiro package as distributed by Debian. See How to fix? for Debian:14 relevant fixed versions and status.

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.