Loading vulnerability…
CVE-2026-44598 is an authenticated open redirect and server-side request forgery vulnerability in Apache Shiro's Jakarta EE integration module (org.apache.shiro:shiro-jakarta-ee). In affected versions, after a successful login the module uses the shiroSavedRequest cookie to determine the page to which the user should be redirected. That cookie was not validated, allowing an attacker with valid credentials to forge it. By supplying a crafted shiroSavedRequest value, the attacker can cause the application to redirect to an untrusted site and can also cause the server itself to issue an HTTP GET request to an arbitrary URL. The issue affects Apache Shiro versions 2.0.0-alpha-0 through 2.1.0 and 3.0.0-alpha-0 through 3.0.0-alpha-1, but only in deployments using the shiro-jakarta-ee integration module.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.