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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

0.0 · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:A/V:D/RE:X/U:Green · score source

EPSS

• CVE-2026-48589: 0.35% estimated exploitation activity in the next 30 days; percentile 28.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

26 May 2026, 13:30 UTC

Last modified by the source

10 Jul 2026, 21:42 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7pq2-fhx9-x464

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48589

Advisory: Apache Shiro’s Jakarta EE module used the HTTP Referer header in certain cases to issue redirect after a user login
IDs: CVE-2026-48589, GHSA-7pq2-fhx9-x464
Record: https://patchnext.com/advisories/cve-2026-48589 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated (CVSS 0.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.shiro:shiro-jakarta-ee 3.0.0-alpha-2, 2.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.shiro:shiro-jakarta-ee: affected >= 2.0-alpha, < 2.2.1; >= 3.0.0-alpha-0, < 3.0.0-alpha-2; fixed in 3.0.0-alpha-2, 2.2.1

## Suggested inspection (read-only)
- Maven org.apache.shiro:shiro-jakarta-ee: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.shiro:shiro-jakarta-ee.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7pq2-fhx9-x464 (GitHub-reviewed advisory GHSA-7pq2-fhx9-x464 lists affected ranges: Maven org.apache.shiro:shiro-jakarta-ee >=2.0-alpha =3.0.0-alpha-0 <3.0.0-alpha-2)

Commands are suggestions: review each one before running it.