Open Redirect in org.apache.shiro:shiro-jakarta-ee (CVE-2026-44598)
Summary
Vulnerability in org.apache.shiro:shiro-jakarta-ee (CVE-2026-44598). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.0-alpha-2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44598 has been found in org.apache.shiro:shiro-jakarta-ee.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade org.apache.shiro:shiro-jakarta-ee to 3.0.0-alpha-2 or later.
If unsure, ask your IT team or search "org.apache.shiro:shiro-jakarta-ee CVE-2026-44598" on the vendor's site.
CVE-2026-44598 (org.apache.shiro:shiro-jakarta-ee) — CWE-601 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 3.0.0-alpha-2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in org.apache.shiro:shiro-jakarta-ee.
Check the vendor advisory for the affected versions of org.apache.shiro:shiro-jakarta-ee.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 3.0.0-alpha-2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.apache.shiro:shiro-jakarta-ee を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.shiro:shiro-jakarta-ee to 3.0.0-alpha-2ステージング環境で 3.0.0-alpha-2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-44598 shiro
References
- advisory nvd.nist.gov
- package github.com
- web shiro.apache.org
- web openwall.com
- web github.com