Categories
CVE-2026-48589 medium CVSS 5.4

Open Redirect in org.apache.shiro:shiro-jakarta-ee (CVE-2026-48589)

Summary

Vulnerability in org.apache.shiro:shiro-jakarta-ee (CVE-2026-48589). Risk of unauthorized operations or information disclosure. Exploitable via Referer header. Mitigation: upgrade to 3.0.0-alpha-2 or later.

Original description

The description as published by the source.

Apache Shiro’s Jakarta EE module used the HTTP Referer header in certain cases to issue redirect after a user login.
In affected versions, insufficient validation of this client-controlled value could allow an attacker to influence the redirect target in applications using the Jakarta EE module.
This issue affects Apache Shiro from 2.0-alpha to 2.2.0, and 3.0.0-alpha-1, only when using shiro-jakarta-ee integration module.

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-48589 has been found in org.apache.shiro:shiro-jakarta-ee.
Attackers can target a specific entry point like Referer header over the network to misuse the product.
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-48589" on the vendor's site.

CVE-2026-48589 (org.apache.shiro:shiro-jakarta-ee) — CWE-601 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: Referer header
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.

❓ What is the problem

A vulnerability (CWE-601) exists in org.apache.shiro:shiro-jakarta-ee. Attackers reach the vulnerable code path via Referer header.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.shiro:shiro-jakarta-ee. Attack surface: Referer header.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.0-alpha-2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.shiro:shiro-jakarta-ee を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.apache.shiro:shiro-jakarta-ee to 3.0.0-alpha-2

    ステージング環境で 3.0.0-alpha-2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.shiro:shiro-jakarta-ee
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0-alpha-0"},{"fixed":"3.0.0-alpha-2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details