CVE-2026-74762 · Package
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only applications that use Apache Shiro with the Remember me feature enabled are exposed. The flaw affects Shiro versions through 3.0.0; applications that do not enable RememberMe are not affected by the cookie-restore path.
Not affected if remember-me-disabled, shiro-above-3.0.0
Who cares apache-shiro, java, web-apps
shiro-core dependency in the build file.rememberMe / CookieRememberMeManager).3.0.0 in use.3.0.1 or later.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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:D/RE:L/U:Amber
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.