CVE-2026-23903

published 9 Feb 2026 · updated 10 Nov 2026

Apache Shiro: Auth bypass when accessing static files only on case-insensitive filesystems

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.0.7.

Authentication Bypass by Alternate Name vulnerability in Apache Shiro. This issue affects Apache Shiro: before 2.0.7. Users are recommended to upgrade to version 2.0.7, which fixes the issue. The issue only effects static files. If static files are served from a case-insensitive filesystem, such as default macOS setup, static files may be accessed by varying the case of the filename in the request. If only lower-case (common default) filters are present in Shiro, they may be bypassed this way. Shiro 2.1.0 and later has a new parameters to remediate this issue shiro.ini: filterChainResolver.caseInsensitive = true application.properties: shiro.caseInsensitive=true Shiro 3.0.0 and later makes this the default in shiro.ini-based configurations. Shiro 3.0.1 and later makes this the default in all configurations, including programmatic and Spring / Spring Boot.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Apache Software Foundation<2.0.72.0.7

Coverage

News and research mentioning this CVE

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-23903 severity on Zeptric[![CVE-2026-23903](https://zeptric.io/badge/cve/CVE-2026-23903.svg)](https://zeptric.io/cve/CVE-2026-23903)