CVE
Apache Shiro Core session fixation in the RememberMe feature
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
- Exploited
- No known exploitation
- Fix
- Fixed in 3.0.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.0.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects Maven packages
- Severity5.9/10CVSS 5.9
- 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.1.
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-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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
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.
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.
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-74762
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: cve.now feed data
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: cve.now feed data
How do I fix CVE-2026-74762?
Upgrade to a fixed version: 3.0.1.Source: cve.now feed data