CVE-2026-23901

published 10 Feb 2026 · updated 10 Feb 2026

Apache Shiro: Brute force attack possible to determine valid user names

1.0LowCVSS 1.0EPSS 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.

Observable Timing Discrepancy vulnerability in Apache Shiro. This issue affects Apache Shiro: from 1.*, 2.* before 2.0.7. Users are recommended to upgrade to version 2.0.7 or later, which fixes the issue. Prior to Shiro 2.0.7, code paths for non-existent vs. existing users are different enough, that a brute-force attack may be able to tell, by timing the requests only, determine if the request failed because of a non-existent user vs. wrong password. The most likely attack vector is a local attack only. Shiro security model  https://shiro.apache.org/security-model.html#username_enumeration  discusses this as well. Typically, brute force attack can be mitigated at the infrastructure level.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Apache Software Foundation<2.0.72.0.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

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