Apache Shiro flaw can let attackers log in with any password

Published

Apache has patched a critical flaw in Shiro, its open-source Java security framework for authentication and access control, that can let an attacker sign in as another user by typing any password at all. The catch is a configuration condition: it only bites when Shiro checks passwords against LDAP and authentication caching has been switched on, which is not the default.

The bug, tracked as CVE-2026-129349, carries a CVSS 4.0 score of 9.1 (critical) and affects all Apache Shiro versions through 3.0.0. The same week Apache also disclosed a separate authentication bypass in its APISIX API gateway, CVE-2026-124679, scored 7.8 (high). Peru's National Center for Digital Security (CNSD) flagged both in its integrated digital security alert No. 227 on November 16. Apache's advisories carry the full detail, and the records are on NVD for CVE-2026-129349 and CVE-2026-124679. Neither advisory reports exploitation in the wild.

One good login unlocks every later one

According to Apache's description, the Shiro flaw lives in the DefaultLdapRealm and JndiLdapRealm components. When authentication caching is enabled, a user's first successful login is cached, and later logins for that user skip the LDAP check entirely. Because DefaultLdapRealm installs a credentials matcher called AllowAllCredentialsMatcher by default, the cached path accepts whatever password is supplied. Anyone who knows a valid username can then authenticate as that user once the account has logged in legitimately.

That makes the exposure narrow but serious where it exists. Teams that turned caching on to reduce load on their directory servers are exactly the ones affected.

APISIX trusts a header it should not

The APISIX bug affects versions 3.18.0 through 3.19.0 of the gateway. Apache says that on routes using the jwe-decrypt plugin with strict set to false, and a forward header distinct from the token header, an unauthenticated client can supply the value that the upstream service treats as plaintext the gateway already decrypted. A similar bypass is possible when the forward-auth plugin is configured with allow_degradation set to true and the authentication service is unavailable. In both cases a backend that relies on the gateway to vouch for a caller can be handed a forged identity.

Upgrade to Shiro 3.0.1 and APISIX 3.20.0

CNSD's bulletin also covered a Microsoft Outlook spoofing flaw, a critical Red Hat Quay bug and a critical FortiManager and FortiAnalyzer issue. Apache has been busy this month too, with a critical HTTP/2 fix for its web server.

Neither bug is the kind that lights up an internet scan, and that is the point. Both turn on a setting someone changed for a good operational reason, which is why the fix starts with knowing how your own login stack is configured.

This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.

Read the full analysis on IntelFusions