CVE-2026-56091 is an improper-authentication vulnerability in Apache Shiro's shiro-guice module when deployed in a web servlet context. A specially crafted HTTP request can cause the application to bypass authentication controls. The issue is analogous to CVE-2020-1957, but affects shiro-guice rather than shiro-spring. Affected releases include Apache Shiro versions through the 2.x series and pre-release 3.0.0 alpha versions through 3.0.0-alpha-1 when the vulnerable module is used in a servlet deployment.
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.
shiro-guice module in a web servlet context until a fixed version can be deployed. Restrict external access to affected applications where feasible and review application-level access controls for sensitive endpoints. The provided content does not include any vendor-specified workaround beyond upgrading.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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authentication bypass vulnerability in Apache Shiro's shiro-guice module when used in a web servlet context, triggered by a specially crafted HTTP request.
An authentication bypass vulnerability in Apache Shiro's shiro-guice module when used in a web servlet context, triggered by a specially crafted HTTP request.
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.