The fix for CVE-2026-23903 https://shiro.apache.org/security-reports.html#cve_2026_23903 was incomplete for
Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 2.3 Low : upgrade to 3.0.2 when convenient.
Data as of 16 Nov 2026, 17:21 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 3.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/S:P/AU:Y/V:D/RE:L/U:GreenExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Apache Shiro and org.apache.shiro/shiro-spring to 3.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Shiroorg.apache.shiro:shiro-spring | Affected
| Fixed in
|
Mavenorg.apache.shiro/shiro-springpkg:maven/org.apache.shiro/shiro-springOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Shiro to version 3.0.2 or later, which contains the complete fix for this issue. Alternatively, if upgrading is not immediately possible, call setCaseInsensitive(true) on the manually-created ShiroFilterFactoryBean to enable case-insensitive path matching and mitigate the vulnerability.
Description
An incomplete fix for CVE-2026-23903 in Apache Shiro 3.0.1 affects applications that manually create ShiroFilterFactoryBean and serve static files from case-insensitive filesystems. The issue causes path matching to remain case-sensitive by default, potentially leading to access control inconsistencies. Applications using Shiro Spring (Boot) Starter to create the bean are not affected. The vulnerability has a low severity score of 2.3. Upgrading to Apache Shiro version 3.0.2 or later or setting caseInsensitive to true on the ShiroFilterFactoryBean mitigates the issue.