Metrics
Affected Vendors & Products
Wed, 11 Feb 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:apache:shiro:*:*:*:*:*:*:*:* |
Tue, 10 Feb 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache shiro |
|
| Vendors & Products |
Apache
Apache shiro |
Tue, 10 Feb 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 09 Feb 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Mon, 09 Feb 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 09 Feb 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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.0.7 and later has a new parameters to remediate this issue shiro.ini: filterChainResolver.caseInsensitive = true application.propertie: shiro.caseInsensitive=true Shiro 3.0.0 and later (upcoming) makes this the default. | |
| Title | Apache Shiro: Auth bypass when accessing static files only on case-insensitive filesystems | |
| Weaknesses | CWE-289 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-02-09T16:17:43.204Z
Reserved: 2026-01-19T01:14:40.103Z
Link: CVE-2026-23903
Updated: 2026-02-09T10:25:43.212Z
Status : Analyzed
Published: 2026-02-09T10:15:57.520
Modified: 2026-02-11T18:30:59.070
Link: CVE-2026-23903