Back to feed
19Track

Apache Shiro: Authorization annotations not always enforced, depending on where they are placed

Apache Software Foundation Apache Shiro · CVE-2026-74763
0 news outlets0 CERTs and agencies1 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable no, technical impact partial, deployment low.

What is it?

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.

Evidence

Technical advisories1Detailed write-ups from security research teams

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
6.3
EPSS
0.5%
First seen
4 d ago
Status
corroborated

All Apache Software Foundation vulnerabilities