Vulnerability · CVE-2026-23901
Observable Timing Discrepancy vulnerability in Apache Shiro.
Published Feb 10, 2026 · catalog updated Feb 10, 2026 · Apache Software Foundation Apache Shiro
Last checked Nov 4, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-23901. EPSS is 0.24%. Act only if a listed version of Apache Software Foundation Apache Shiro is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Low1.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Version ranges on file
- Affected products
- vendor Apache Software Foundation Apache Shiro 0 <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 disc
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Apache Software Foundation Apache Shiro 0 <2.0.70 <2.0.7
How to fix CVE-2026-23901
Upgrade
CVE-2026-23901 lists a fix boundary at 2.0.7. Compare the installed build with that boundary before you change production.
Version check
Seen in 0 <2.0.7
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-23901. EPSS is 0.24%. Act only if a listed version of Apache Software Foundation Apache Shiro is installed.
Which versions are affected?
Compare what you have installed with Apache Software Foundation Apache Shiro 0 <2.0.7 0 <2.0.7. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Feb 10, 2026 · EUVD
Detected
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 fai
Feb 10, 2026 · EUVD
Updated
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 fai
Sources
- CVE.orgVulnerability recordCVE-2026-23901
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-23901
30-day exploitation probability 0.24%
first.org - EUVDVulnerability recordEUVD-2026-6879
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 di
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 4, 2026
- CVE.orgNov 4, 2026
- EUVDNov 3, 2026