---
id: "CVE-2026-74762"
page: "https://infrastack.ai/live/CVE-2026-74762"
kind: "vulnerability"
aliases: ["CVE-2026-74762"]
title: "Apache Shiro: Remember-me login keeps old session ID, enabling session fixation"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-shiro", "java", "package", "web-apps"]
not_affected_if: ["remember-me-disabled", "shiro-above-3.0.0"]
published_at: "2026-11-16T14:17:08+00:00"
first_seen_at: "2026-11-16T14:37:00+00:00"
updated_at: "2026-11-16T14:37:21+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74762", "first_seen_at": "2026-11-16T14:37:00+00:00"}]
exploit_sources: []
---

# Apache Shiro: Remember-me login keeps old session ID, enabling session fixation

Link for people: https://infrastack.ai/live/CVE-2026-74762 (this .md is for agents)

When a user is logged in through Shiro's Remember me cookie, the existing session is not invalidated and no new session ID is issued, and session IDs in URLs are accepted even when URL rewriting is disabled. An attacker who plants a known session ID in a victim's browser can hijack the session after the victim logs in.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the application uses Apache Shiro and its version, for example by reviewing the `shiro-core` dependency in the build file.
- Confirm whether RememberMe is enabled in the Shiro configuration (`rememberMe` / CookieRememberMeManager).
- Look for any version of Shiro through `3.0.0` in use.

## Fix

- Apache Shiro: upgrade to `3.0.1` or later.

## Timeline

- 2026-11-16T14:37:00+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-74762

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
