CVE-2026-114737 · Package
NO FIX YET · SEE WHAT TO DO
Apache Shiro 3.0.1 applications that create ShiroFilterFactoryBean manually still match paths case-sensitively by default, an incomplete fix for CVE-2026-23903. On case-insensitive filesystems serving static files, an attacker can request a path with different letter case to bypass access filters.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only applications that create ShiroFilterFactoryBean manually and serve static files from a case-insensitive filesystem are affected. Applications where Shiro Spring (Boot) Starter creates the bean are not affected.
Not affected if case-sensitive-filesystem, no-static-files, spring-boot-starter-created-bean
Who cares apache-shiro, java, macos, spring-boot, windows
ShiroFilterFactoryBean manually in code rather than letting Shiro Spring Boot Starter create it.3.0.1.3.0.2 or later.setCaseInsensitive(true) on the ShiroFilterFactoryBean.The fix for CVE-2026-23903 https://shiro.apache.org/security-reports.html#cve_2026_23903 was incomplete for manually-created ShiroFilterFactoryBean, which still matched paths case-sensitively by default. This issue affects Apache Shiro version 3.0.1, only when ShiroFilterFactoryBean is created manually by the application and static files are served from a case-insensitive filesystem. Applications that let Shiro Spring (Boot) Starter create the bean are not affected.
Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue. Alternatively, call setCaseInsensitive(true) on the ShiroFilterFactoryBean.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:X/V:D/RE:L/U:Green
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.