# CVE-2026-44598: Apache Shiro Jakarta EE module: Open redirect and SSRF (requires valid credentials) > Authenticated attackers can exploit unvalidated cookies in Apache Shiro's Jakarta EE module to trigger SSRF and open redirects. - **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/AU:Y/R:A/V:D/RE:L/U:Green`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 25 May 2026 - **Updated:** 26 May 2026 - **Also known as:** GHSA-wpqm-4gwx-w843, UBUNTU-CVE-2026-44598 ## What is CVE-2026-44598? CVE-2026-44598 is a medium-severity server-side request forgery vulnerability in Apache Shiro Jakarta EE module, published on 25 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-918 (Server-Side Request Forgery), CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2026-44598? 4 open source packages ship an affected version, including org.apache.shiro:shiro-jakarta-ee. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.shiro:shiro-jakarta-ee` | Maven | From 2.0.0-alpha-0 | 2.2.0 | | `org.apache.shiro:shiro-jakarta-ee` | Maven | From 2.0.0-alpha-0 | 2.2.0 | | `org.apache.shiro:shiro-jakarta-ee` | Maven | From 3.0.0-alpha-1 | 3.0.0-alpha-2 | | `org.apache.shiro:shiro-jakarta-ee` | Maven | From 3.0.0-alpha-1 | 3.0.0-alpha-2 | Products: Apache Shiro. ## How do I fix CVE-2026-44598? Upgrade org.apache.shiro:shiro-jakarta-ee to a fixed version for your release line: 2.2.0 or 3.0.0-alpha-2. ## Is CVE-2026-44598 being exploited? There is no known exploitation of CVE-2026-44598 in the wild and no public exploit code. ## Other vulnerabilities in Apache Shiro Jakarta EE module - [CVE-2023-34478](https://insights.sbomify.com/CVE-2023-34478/): Path Traversal in Apache Shiro (critical 9.8) - [CVE-2022-40664](https://insights.sbomify.com/CVE-2022-40664/): Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher (critical 9.8) - [CVE-2022-32532](https://insights.sbomify.com/CVE-2022-32532/): Authentication Bypass Vulnerability (critical 9.8) - [CVE-2021-41303](https://insights.sbomify.com/CVE-2021-41303/): Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass (critical 9.8) - [CVE-2020-17523](https://insights.sbomify.com/CVE-2020-17523/): Authentication bypass in Apache Shiro (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-44598 and fix it if it is affected. What it is: CVE-2026-44598 is a medium-severity server-side request forgery vulnerability in Apache Shiro Jakarta EE module, published on 25 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-44598 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.shiro:shiro-jakarta-ee (Maven): affected from 2.0.0-alpha-0; fixed in 2.2.0 - org.apache.shiro:shiro-jakarta-ee (Maven): affected from 2.0.0-alpha-0; fixed in 2.2.0 - org.apache.shiro:shiro-jakarta-ee (Maven): affected from 3.0.0-alpha-1; fixed in 3.0.0-alpha-2 - org.apache.shiro:shiro-jakarta-ee (Maven): affected from 3.0.0-alpha-1; fixed in 3.0.0-alpha-2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-44598/ (Markdown: https://insights.sbomify.com/CVE-2026-44598/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44598 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44598 - OSV: https://osv.dev/vulnerability/CVE-2026-44598 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-44598/ Summaries are generated and may contain mistakes; the official description above is the record.