Summary
Apache Shiro Vulnerable to Open Redirect, Server-Side Request Forgery
With valid login credentials, URL Redirection to Untrusted Site ('Open Redirect'), Server-Side Request Forgery (SSRF) vulnerability in Apache Shiro.
This issue affects Apache Shiro from 2.0-alpha to 2.1.0, and 3.0.0-alpha-1, only when using shiro-jakarta-ee integration module.
Users are recommended to upgrade to version 2.1.1, or 3.0.0-alpha-2 or later, which fixes the issue by encrypting the cookie.
After successful login, Jakarta EE integration module uses shiroSavedRequest cookie to redirect to a particular web page after login.
This cookie was not validated, and can be forged to send a HTTP GET request from the server itself to an arbitrary URL from the cookie.
Impact
Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.shiro:shiro-jakarta-ee to 2.2.0 or later; org.apache.shiro:shiro-jakarta-ee to 3.0.0-alpha-2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-44598? CVE-2026-44598 is a medium-severity open redirect vulnerability in org.apache.shiro:shiro-jakarta-ee (maven), affecting versions >= 2.0.0-alpha-0, < 2.2.0. It is fixed in 2.2.0, 3.0.0-alpha-2. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
- Which versions of org.apache.shiro:shiro-jakarta-ee are affected by CVE-2026-44598? org.apache.shiro:shiro-jakarta-ee (maven) versions >= 2.0.0-alpha-0, < 2.2.0 is affected.
- Is there a fix for CVE-2026-44598? Yes. CVE-2026-44598 is fixed in 2.2.0, 3.0.0-alpha-2. Upgrade to this version or later.
- Is CVE-2026-44598 exploitable, and should I be worried? Whether CVE-2026-44598 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-44598 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-44598?
- Upgrade
org.apache.shiro:shiro-jakarta-eeto 2.2.0 or later - Upgrade
org.apache.shiro:shiro-jakarta-eeto 3.0.0-alpha-2 or later
- Upgrade