Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2026-48589 — shiro-jakarta-ee

MEDIUM

CVE-2026-48589 is a medium-severity (CVSS 5.4) Open Redirect vulnerability in org.apache.shiro:shiro-jakarta-ee. A fix is available for org.apache.shiro:shiro-jakarta-ee — see the affected versions and patch details below.

Apache Shiro’s Jakarta EE module used the HTTP Referer header in certain cases to issue redirect after a user login

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-48589.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk
0.00%0.32%0.64%0.95%0.1%0.5%Jun 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-48589 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.apache.shiro:shiro-jakarta-ee☕org.apache.shiro:shiro-jakarta-ee

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.shiro:shiro-jakarta-ee≥ 2.0-alpha&&< 2.2.12.2.1org.apache.shiro:shiro-jakarta-ee:2.2.1
☕Mavenorg.apache.shiro:shiro-jakarta-ee≥ 3.0.0-alpha-0&&< 3.0.0-alpha-23.0.0-alpha-2org.apache.shiro:shiro-jakarta-ee:3.0.0-alpha-2

Affected Products

1 product · 2 configurations
Application
shiroapache
≥ 2.0.0 && < 2.2.1
1 version
3.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-jakarta-ee, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.shiro:shiro-jakarta-ee to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-48589 is resolved across your whole dependency graph.

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat ships Apache Shiro's Jakarta EE integration module (shiro-jakarta-ee) as a bundled dependency in EAP XP. A flaw was found where insufficient validation of the HTTP Referer header could allow an attacker to influence the redirect target after user login, potentially redirecting users to malicious sites. This…

Workaround published by Red Hat
Ensure that applications using Apache Shiro's Jakarta EE module do not rely solely on the HTTP Referer header for post-login redirect decisions. Where possible, configure explicit redirect URLs in the application rather than accepting client-supplied values.
Source: Red Hat security advisory for CVE-2026-48589 (CC BY 4.0)

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-48589 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-48589: shiro-jakarta-ee — Fixed in 2.2.1