CVSS 4.0
0.0 noneCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y/R:A/V:D/U:GreenInfo (0.0) in apache shiro. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.shiro:shiro-jakarta-ee 2.2.1, 3.0.0-alpha-2.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y/R:A/V:D/U:GreenCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:Norg.apache.shiro:shiro-jakarta-ee (Maven): fixed in 2.2.1, 3.0.0-alpha-2Explain CVE-2026-48589 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48589?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48589?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48589 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Shiro | from 2.0.0-alpha-0 through 2.2.0 |
| Apache Software Foundation Apache Shiro | from 3.0.0-alpha-0 through 3.0.0-alpha-1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-7pq2-fhx9-x464 | Maven | org.apache.shiro:shiro-jakarta-ee | >=2.0-alpha <2.2.1 | 2.2.1 |
| GHSA-7pq2-fhx9-x464 | Maven | org.apache.shiro:shiro-jakarta-ee | >=3.0.0-alpha-0 <3.0.0-alpha-2 | 3.0.0-alpha-2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 20.04:LTS, 22.04:LTS, 25.10 and 5 more | shiro | no fix listed | UBUNTU-CVE-2026-48589 |
From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.
Red Hat rates this Moderate.
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 vulnerability only affects applications using the shiro-jakarta-ee module specifically, not Apache Shiro core.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat JBoss Enterprise Application Platform Expansion Pack | shiro-jakarta-ee | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-48589.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.