How severe is CVE-2026-44598?

No CVSS score has been assigned to CVE-2026-44598 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-44598?

CVE-2026-44598 affects the following packages: org.apache.shiro:shiro-jakarta-ee (Maven), org.apache.shiro:shiro-jakarta-ee (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-44598?

Update org.apache.shiro:shiro-jakarta-ee to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44598 is resolved across your whole dependency graph.

How do I detect CVE-2026-44598 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-jakarta-ee, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-44598 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2026-44598 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-44598 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-44598?

CVE-2026-44598 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-44598?

CVE-2026-44598 is classified as Open Redirect (CWE-601), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-44598 published, and has it been updated?

CVE-2026-44598 was published on May 26, 2026 and was last updated on June 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-44598 — shiro-jakarta-ee

CVE-2026-44598 is a Open Redirect vulnerability in org.apache.shiro:shiro-jakarta-ee. A fix is available for org.apache.shiro:shiro-jakarta-ee — see the affected versions and patch details below.

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

Published

May 26, 2026

Updated

Jun 30, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44598.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.13%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.shiro:shiro-jakarta-ee☕org.apache.shiro:shiro-jakarta-ee

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.shiro:shiro-jakarta-ee`	≥ 2.0.0-alpha-0&&< 2.2.0	2.2.0`org.apache.shiro:shiro-jakarta-ee:2.2.0`
☕Maven	`org.apache.shiro:shiro-jakarta-ee`	≥ 3.0.0-alpha-1&&< 3.0.0-alpha-2	3.0.0-alpha-2`org.apache.shiro:shiro-jakarta-ee:3.0.0-alpha-2`

Affected Products

1 product · 2 configurations

Application

shiroapache

≥ 2.0.0 && < 2.1.1

1 version

3.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-jakarta-ee, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.shiro:shiro-jakarta-ee to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44598 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2026-44598 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works