---
id: "CVE-2026-74763"
page: "https://infrastack.ai/live/CVE-2026-74763"
kind: "vulnerability"
aliases: ["CVE-2026-74763"]
title: "Apache Shiro: authorization annotations skipped on some class and interface hierarchies"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-shiro", "java", "package", "shiro-aspectj", "shiro-cdi", "shiro-guice", "shiro-jakarta-ee"]
not_affected_if: ["no-shiro-annotations", "shiro-core-only"]
published_at: "2026-11-16T14:17:08+00:00"
first_seen_at: "2026-11-16T14:37:00+00:00"
updated_at: "2026-11-16T14:37:20+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74763", "first_seen_at": "2026-11-16T14:37:00+00:00"}]
exploit_sources: []
---

# Apache Shiro: authorization annotations skipped on some class and interface hierarchies

Link for people: https://infrastack.ai/live/CVE-2026-74763 (this .md is for agents)

Apache Shiro annotations such as @RequiresRoles and @RequiresPermissions are not always enforced when declared on interfaces, or on classes and superclasses in shiro-guice and shiro-aspectj. An unauthorized caller can invoke methods that should be protected.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Look for Apache Shiro in dependencies, for example `shiro-guice`, `shiro-aspectj`, `shiro-cdi` or `shiro-jakarta-ee`.
- Check whether authorization annotations are declared on interfaces or superclasses rather than on each implementing method.

## Fix

- Apache Shiro: upgrade to `3.0.2` or later.
- Alternative stated by the source: declare authorization annotations directly on each protected implementing method.

## Timeline

- 2026-11-16T14:37:00+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-74763

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
