Home › Vulnerabilities

Apache Shiro Flaw CVE-2026-129349: Update Now

Published November 15, 2026 · Last updated November 15, 2026

Apache CVE Critical Patch

The short version: CVE-2026-129349 is a critical-severity security flaw in Apache Shiro. The National Vulnerability Database (NVD) published it on November 15, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on November 15, 2026, CISA had not added CVE-2026-129349 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

CVE-2026-129349 is a critical login flaw in Apache Shiro, an open-source Java security framework. The Shiro project describes Shiro as a framework "that performs authentication, authorization, cryptography, and session management" for Java applications. In affected setups, someone who knows a valid username can log in as that user with any password.

The Shiro project announced the flaw on November 14, 2026, and fixed it in Shiro 3.0.1. The CVE record was published on November 15. There is no public report of attacks using it, and it is not in the U.S. Cybersecurity and Infrastructure Security Agency's (CISA) Known Exploited Vulnerabilities catalog.

Who is affected

Not every Shiro application is exposed. According to the Shiro project's advisory, the flaw 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."

In other words, three things must all be true:

  • The application uses a Shiro version before 3.0.1. The CVE record lists the affected package as org.apache.shiro:shiro-core.
  • It checks logins against an LDAP directory using Shiro's DefaultLdapRealm or JndiLdapRealm.
  • Authentication caching is switched on for that realm. It is off by default.

What goes wrong

Normally, Shiro's LDAP realm verifies a password by binding (logging in) to the LDAP server. The advisory explains that when caching is on, "after a user logs in successfully once, subsequent logins for that user succeed with any password." A cached login skips the LDAP check, and the credentials matcher that DefaultLdapRealm installs by default, AllowAllCredentialsMatcher, "accepts any credentials." The result, per the advisory, is "allowing an attacker who knows a valid username to authenticate as that user."

The CVE record classifies the weakness as CWE-287, improper authentication.

Severity and who scored it

The Apache Software Foundation, the CVE Numbering Authority for Shiro, scored the flaw CVSS 4.0 9.1 (Critical), vector AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N. That means it is reachable over the network with no privileges and no user interaction, but with attack requirements present, and with high impact on confidentiality and integrity. NVD lists Apache's score as a Secondary source; it had not added its own score when we checked. Shiro's security page rates the issue "Critical."

The fix

The advisory's mitigation, in full: "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."

Shiro's security page also lists other lower-severity issues that affect 3.0.1 and are fixed in 3.0.2. One of them, CVE-2026-129347 (rated Low), concerns SimpleCredentialsMatcher treating an empty stored credential as a match for an empty password, "only when accounts with an empty stored credential exist." Moving to 3.0.2 or later addresses those as well.

What to do

  • Developers and maintainers of Java applications that use Shiro's LDAP realms: check whether authenticationCachingEnabled is set to true on DefaultLdapRealm or JndiLdapRealm. If it is, upgrade Shiro to 3.0.1 or later (3.0.2 or later also covers the related low-severity fixes).
  • If you cannot upgrade right away: turn authentication caching off on the LDAP realm, or configure a credentials matcher that verifies credentials against the cached authentication info, as the advisory describes.
  • Administrators of software built on Shiro: ask the vendor whether the product uses a Shiro LDAP realm with caching enabled and when it will ship Shiro 3.0.1 or later.

Timeline

  • November 14, 2026, 12:37 a.m. ET: the Shiro project announces the flaw on its user mailing list.
  • November 15, 2026: the CVE record is published and NVD receives it.

Apache Shiro credits Joshua Rogers with reporting the issue.

Sources: Apache Shiro announcement on the the address listed on shiro.apache.org mailing list; Apache Shiro security reports page; the CVE record published by the Apache Software Foundation; NVD.

What the official record says about CVE-2026-129349

The record was filed by apache.org. In its own words: "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."

Why Shiro admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on apache.org rated CVE-2026-129349 9.1 (Critical) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Shiro running is none. Scoring string: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:C/RE:L/U:Red.

Affected Shiro releases

According to the record, these releases are vulnerable:

  • versions before 3.0.1

The type of bug behind CVE-2026-129349

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-287, Improper Authentication. MITRE describes this class of bug as follows: "When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct."

Vendor remediation for CVE-2026-129349

The vendor advisory remediation for operators of Shiro, quoted for this page, is: "Upgrade Apache Shiro (org.apache.shiro:shiro-core) to 3.0.1 or later. Version 3.0.2 or later also covers related low-severity issues that affect 3.0.1, including CVE-2026-129347. 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."

What to do about it

  • Update now: Upgrade Apache Shiro (org.apache.shiro:shiro-core) to 3.0.1 or later. Version 3.0.2 or later also covers related low-severity issues that affect 3.0.1, including CVE-2026-129347. 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.
  • Who should act: IT teams, managed service providers, and developers who run or ship Shiro. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Apache (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 15, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-129349. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-129349 record details from CISA and NVD

  • Attack complexity for CVE-2026-129349: low
  • CVE-2026-129349 attack requirements: present
  • Impact on connected systems: secrecy none, integrity none, availability none.
  • Who mapped the weakness type: the address listed on apache.org (Primary)
  • References in the NVD record: 2.

Dates to know

  • November 15, 2026: NVD publishes CVE-2026-129349.
  • November 15, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-129349 is not listed.
  • November 15, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.