dbcve.org
ShiroApplication · Apache

CVE-2026-44598

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-25
Fix available
A fix is available. Upgrade to 2.1.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
With valid login credentials, URL Redirection to Untrusted Site ('Open Redirect'), Server-Side Request Forgery (SSRF) vulnerability in Apache Shiro. This issue affects Apache Shiro from 2.0-alpha to 2.1.0, and 3.0.0-alpha-1, only when using shiro-jakarta-ee integration module. Users are recommended to upgrade to version 2.1.1, or 3.0.0-alpha-2 or later, which fixes the issue by encrypting the cookie. After successful login, Jakarta EE integration module uses shiroSavedRequest cookie to redirect to a particular web page after login. This cookie was not validated, and can be forged to send a HTTP GET request from the server itself to an arbitrary URL from the cookie.

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

The shiroSavedRequest cookie in Apache Shiro's Jakarta EE integration module (versions 2.0-alpha through 2.1.0 and 3.0.0-alpha-1) is not validated after successful login. This allows authenticated attackers to forge cookie values containing arbitrary URLs, causing the server to make SSRF requests to attacker-controlled destinations or redirect users to malicious sites.

MitigationUpgrade Apache Shiro to version 2.1.1 or 3.0.0-alpha-2 or later, which encrypts the shiroSavedRequest cookie to prevent tampering. Verify post-login redirects function correctly after upgrading.

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.1.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
    Locate the Shiro JAR files in your deployment (typically in WEB-INF/lib or build dependencies) and check the version from the filename (shiro-core-X.X.X.jar) or inspect the MANIFEST.MF file within the JAR
    Affected if The installed version is 2.0.0-alpha through 2.1.0, or exactly 3.0.0-alpha-1
  2. Confirm Jakarta EE integration module is in use
    Check for the presence of shiro-jakartaee-module JAR in the deployment or verify it is listed as a dependency in your build configuration (pom.xml, build.gradle)
    Affected if The Jakarta EE integration module (shiro-jakartaee-module) is included in the deployment
  3. Verify shiroSavedRequest cookie handling is active
    Examine the Shiro configuration (shiro.ini, Spring XML, or annotation-based config) for the session management settings and verify whether savedRequest handling is enabled by default for login redirects
    Affected if Login redirection using the shiroSavedRequest cookie is in use, which is the default behavior for post-login redirects in affected versions
  4. Inspect cookie configuration
    Review the HttpServletResponse headers during a login flow to confirm a cookie named 'shiroSavedRequest' is being set, and check if the cookie value appears unencrypted or tamperable
    Affected if A shiroSavedRequest cookie is present and its value is not encrypted or validated
  5. Compare against fixed versions
    Cross-reference your identified version against the fixed releases: 2.1.1 or 3.0.0-alpha-2 or later
    Affected if The deployed version is earlier than 2.1.1 (for 2.x line) or is 3.0.0-alpha-1 (for 3.x line)

You are affected if Apache Shiro with the Jakarta EE integration module is deployed and the installed version falls within 2.0.0-alpha through 2.1.0 or equals 3.0.0-alpha-1, with the shiroSavedRequest cookie being used 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.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade Apache Shiro to version 2.1.1 or 3.0.0-alpha-2 or later, which encrypts the shiroSavedRequest cookie to prevent tampering. Verify post-login redirects function correctly after upgrading.

Recommended fix High confidence

2.1.1 or 3.0.0-alpha-2+

  1. 1. Identify all applications using Apache Shiro with the shiro-jakarta-ee integration module
  2. 2. Check the current Shiro version in your project dependencies (pom.xml, build.gradle, etc.)
  3. 3. If using Shiro version >= 2.0.0 and < 2.1.1, upgrade the shiro.version property to 2.1.1 or later in your dependency management
  4. 4. If using Shiro version 3.0.0 (specifically 3.0.0-alpha-1), upgrade to 3.0.0-alpha-2 or later
  5. 5. Rebuild and test the application to ensure the upgrade does not break existing functionality
  6. 6. Deploy the updated application to all affected environments
Caveat Upgrade should be low-risk; the fix adds cookie encryption without breaking existing functionality

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

Fix this in Shiro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44598 — 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-44598 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