AI Science Tracker

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

Apache Software Foundation Apache Shiro · AI involvement attributed to AISLE AI-native discovery engine (model/version not disclosed)

Finding and attribution

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.

Product: Apache Software Foundation Apache Shiro. AI system: AISLE AI-native discovery engine (model/version not disclosed). Team / organization: AISLE.

CVE identifiers: CVE-2026-74763.

AI and human contribution (source account): AISLE’s CVE Discoveries index lists this CVE among those its AI-native engine discovered, and the individual AISLE page says “Discovered by AISLE”. The CNA record credits “n0mi1k; Joshua Rogers; Wentao He; Lenny Primak”; a credited human name is not itself AI attribution, which rests on AISLE’s page. The model/version and the division of work between the engine and human researchers are not disclosed.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: Public CVE disclosure is dated 2026-11-16. AISLE’s case page timeline shows 2026-11-16, used as the AI-attribution date. The cited sources establish an assigned vulnerability, not exploitation in the wild or zero-day status.

Remediation status: fix documented. 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. Confirm the distribution-specific backport before relying on a version number.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 16 Nov 2026. AI attribution dated 16 Nov 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 6.3. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-74763: CVSS 4.0 · 6.3 (Medium) · 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. apache (CNA; CVE Program record) · checked 17 Nov 2026.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: 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. Confirm the distribution-specific backport before relying on a version number.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases