Skip to main content
Menu
CVEs

CVE

Apache authorization bypass in security annotations

CVE-2026-74763EUVD-2026-126383GHSA-WPCF-J6J4-3PQ6

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

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.0.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.0.2.

Published
Last modified
Reference
Last checked
33/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Apache Shiro's authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced when declared on interfaces, classes, or superclasses, depending on the module in use. An unauthorized caller can reach remotely, without logging in, methods that should be protected, which may allow a loss of confidentiality and integrity.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

33Pcve.now Index 33 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.0.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-74763 (Apache Shiro: Authorization annotations not always enforced, depending on where they are placed), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-74763 (entry last updated 2026-11-16):
Affected:
- Maven package org.apache.shiro:shiro-guice: fixed in 3.0.2
- Maven package org.apache.shiro:shiro-aspectj: fixed in 3.0.2
- Maven package org.apache.shiro:shiro-cdi: from 2.0.0-alpha-0, fixed in 3.0.2
- Maven package org.apache.shiro:shiro-jakarta-ee: from 2.0.0-alpha-0, fixed in 3.0.2
Fixed versions: 3.0.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-74763 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-74763 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/gfy3dyh5vfocp34l0bc6dy8gbbjgs3pf
- http://www.openwall.com/lists/oss-security/2026/11/14/4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-74763
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-74763"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-74763

Is CVE-2026-74763 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-74763?

org.apache.shiro:shiro-guice (Maven): before 3.0.2. org.apache.shiro:shiro-aspectj (Maven): before 3.0.2. org.apache.shiro:shiro-cdi (Maven): from 2.0.0-alpha-0 before 3.0.2. org.apache.shiro:shiro-jakarta-ee (Maven): from 2.0.0-alpha-0 before 3.0.2.Source: cve.now feed data

How do I fix CVE-2026-74763?

Upgrade to a fixed version: 3.0.2.Source: cve.now feed data