Skip to content

← Public intelligence

Maven package

org.apache.shiro:shiro-jakarta-ee

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedMavenPublished

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

    CVE-2026-48589 · GHSA-7pq2-fhx9-x464

    Affected
    • Maven org.apache.shiro:shiro-jakarta-ee >= 2.0-alpha, < 2.2.1; >= 3.0.0-alpha-0, < 3.0.0-alpha-2
    Fixed in
    3.0.0-alpha-22.2.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.0.0-alpha-2 (pre-release) or 2.2.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.1MavenPublished

    Apache Shiro Vulnerable to Open Redirect, Server-Side Request Forgery

    CVE-2026-44598 · GHSA-wpqm-4gwx-w843

    Affected
    • Maven org.apache.shiro:shiro-jakarta-ee >= 2.0.0-alpha-0, < 2.2.0; >= 3.0.0-alpha-1, <= 3.0.0-alpha-1
    Fixed in
    2.2.03.0.0-alpha-2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.0.0-alpha-2 (pre-release) or 2.2.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →