dbcve.org
ShiroApplication · Apache

CVE-2026-48589

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-25
Fix available
A fix is available. Upgrade to 2.2.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Shiro’s Jakarta EE module uses the HTTP Referer header to determine redirect targets after user login. Since the Referer header is client-controlled and not properly validated, attackers can craft malicious links that redirect authenticated users to attacker-controlled websites after successful authentication, creating an open redirect vulnerability.

MitigationUpgrade to a patched version of Apache Shiro when available, or implement server-side allowlist validation of redirect targets to ensure they point only to trusted internal URLs before performing the redirect.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShiroApplication
Affected:>= 2.0.0, < 2.2.1= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Shiro version in use
    Inspect your project's dependency manifest (Maven pom.xml, Gradle build.gradle, or the JAR file's MANIFEST.MF) to locate the shiro-core or shiro-web version number
    Affected if The version is >= 2.0.0 AND < 2.2.1, or equals 3.0.0
  2. Confirm shiro-jakarta-ee module is present
    Check your dependencies or application classpath for the shiro-jakarta-ee JAR file. This vulnerability exists only in this specific integration module
    Affected if The shiro-jakarta-ee module is included in your runtime dependencies
  3. Identify redirect configuration in shiro.ini or JavaConfig
    Search your Shiro configuration files for redirect settings. Look for any redirect or successUrl parameters that may utilize the Referer header for post-login navigation
    Affected if Your configuration specifies redirect behavior that could derive its target from the HTTP Referer header
  4. Review login flow implementation for Referer usage
    Examine your application's login controller or Shiro filter chain to determine if the Referer header is read and used for constructing post-authentication redirect URLs
    Affected if Your application code reads the Referer header and uses it to determine where to redirect users after successful authentication

You are affected if you are running Apache Shiro version 2.0.0 through 2.2.0 or version 3.0.0, AND the shiro-jakarta-ee module is present in your dependencies, AND your application uses the Referer header for post-login redirects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.1 or later
Fixed in 2.2.1
Interim mitigation

Upgrade to a patched version of Apache Shiro when available, or implement server-side allowlist validation of redirect targets to ensure they point only to trusted internal URLs before performing the redirect.

Recommended fix High confidence

Shiro 2.x -> 2.2.1; Shiro 3.x -> 3.0.1 or later

  1. 1. Identify all applications using Apache Shiro with the shiro-jakarta-ee integration module
  2. 2. Determine the current Shiro version in use from project dependencies (e.g., pom.xml, build.gradle)
  3. 3. For Shiro 2.x line: upgrade shiro-jakarta-ee module to version 2.2.1 or later
  4. 4. For Shiro 3.x line: upgrade shiro-jakarta-ee module to version 3.0.1 or later (the first fixed release after 3.0.0)
  5. 5. Rebuild and redeploy the application
  6. 6. Test the login flow to verify redirect functionality works correctly
  7. 7. Verify that arbitrary Referer header values no longer influence the redirect target
Caveat Minimal risk - this is a security fix; however, validate that custom redirect logic does not rely on the previous vulnerable behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shiro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48589 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data