{"published_count":667,"discovered_count":673,"count":4,"cves":[{"cve_id":"CVE-2026-129349","title":"Arbitrary account takeover when authentication caching is enabled","description":"When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password.\nA 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.\nThis 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.\n\nMitigation: Upgrade to version 3.0.1 or later, which fixes the issue by no longer installing AllowAllCredentialsMatcher by default.\nAlternatively, 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.","severity":"critical","cvss_score":9.1,"cvss_vector":"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/S:N/AU:Y/R:U/V:C/RE:L/U:Red","cwe":"CWE-287","product":"Apache Shiro","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-129349","published":"2026-11-15"},{"cve_id":"CVE-2026-74763","title":"Authorization annotations not always enforced, depending on where they are placed","description":"Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies.\nAnnotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules.\nIn addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected.\nThis issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared.\n\nMitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence.\nAlternatively, declare authorization annotations directly on each protected implementing method.","severity":"medium","cvss_score":6.3,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/V:D/RE:L/U:Amber","cwe":"CWE-862","product":"Apache Shiro","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-74763","published":"2026-11-16"},{"cve_id":"CVE-2026-88019","title":"Saved form replay may weaken cookie security and expose form data","description":"When Apache Shiro is used with the Jakarta EE integration module, the automatic form saving feature weakens the security of a form that is resubmitted after login.\nCookies set by the application during the resubmission could lose their security attributes, such as `Secure` and `SameSite`.\nIn addition, the resubmitted form data and cookies could be sent to an untrusted host.\nThis issue affects Apache Shiro from 2.0.0-alpha through 3.0.1, only when using `shiro-jakarta-ee` integration module with form saving enabled (the default).\n\nMitigation: Upgrade to version 3.0.2 or later, which no longer replays the form over the network, and avoids this class of issues entirely.\nAlternatively, you can set the `org.apache.shiro.form-resubmit-host` (String) and `org.apache.shiro.form-resubmit-port` (Integer) system properties to restrict the host and port that Shiro will connect to when resubmitting a form.","severity":"medium","cvss_score":6.0,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/R:U/V:D/RE:L/U:Amber","cwe":"CWE-918","product":"Apache Shiro","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-88019","published":"2026-11-16"},{"cve_id":"CVE-2026-129348","title":"PropertiesRealm reload does not remove deleted users or narrowed permissions","description":"When PropertiesRealm reloads its properties file, removed users and narrowed permissions could remain in effect.\nThis issue affects all Apache Shiro versions through 3.0.1, only when PropertiesRealm`loads its properties from a file, which is reloaded periodically by default.\n\nMitigation: Upgrade to version 3.0.2 or later, which fixes the issue.\nAlternatively, restart the application after removing users or narrowing permissions.","severity":"low","cvss_score":2.3,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/V:D/RE:L/U:Green","cwe":"CWE-269","product":"Apache Shiro","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-129348","published":"2026-11-16"}]}