Answer in brief
CVE-2026-74763 records a Medium severity (CVSS 6.3) vulnerability in Apache Shiro: Authorization annotations not always enforced, depending on where they are placed. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/org.apache.shiro:shiro-aspectj (generic), Apache Software Foundation/org.apache.shiro:shiro-cdi (generic), Apache Software Foundation/org.apache.shiro:shiro-guice (generic), Apache Software Foundation/org.apache.shiro:shiro-jakarta-ee (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/org.apache.shiro:shiro-aspectj (generic), Apache Software Foundation/org.apache.shiro:shiro-cdi (generic), Apache Software Foundation/org.apache.shiro:shiro-guice (generic), Apache Software Foundation/org.apache.shiro:shiro-jakarta-ee (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/org.apache.shiro:shiro-aspectjgeneric | >=0 <3.0.2 | 3.0.2 |
| Apache Software Foundation/org.apache.shiro:shiro-cdigeneric | >=2.0.0-alpha-0 <3.0.2 | 3.0.2 |
| Apache Software Foundation/org.apache.shiro:shiro-guicegeneric | >=0 <3.0.2 | 3.0.2 |
| Apache Software Foundation/org.apache.shiro:shiro-jakarta-eegeneric | >=2.0.0-alpha-0 <3.0.2 | 3.0.2 |
Published upstream
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 16, 2026
Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies. Annotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules. In 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. This issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared. Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence. Alternatively, declare authorization annotations directly on each protected implementing method.
Quoted source text, attributed separately from HOL analysis.