Cyber Resilience

CVE-2026-23901

Apache Shiro ≤ 2.0.7

Published
10 February 2026
Modified
12 February 2026
CVSS Score v4 1.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:L/VI:N/VA:N/SC:L/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:N/AU:Y/R:A/V:C/RE:L/U:Green
EPSS Score 0.0022 12th percentile
Risk Priority 15 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-23901 is a low-severity Observable Timing Discrepancy (CWE-208) vulnerability in Apache Shiro. Its CVSS base score is 1.0 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Password Guessing (T1110.001); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.…

more

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.

CWE(s)
CWE-208

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
attack.mitre.org →
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
attack.mitre.org →
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
attack.mitre.org →
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
attack.mitre.org →
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
attack.mitre.org →
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-49506Same vendor: Apache
CVE-2026-43514Same vendor: Apache
CVE-2026-44598Same product: Apache Shiro
CVE-2026-33006Same vendor: Apache
CVE-2026-43828Same product: Apache Shiro
CVE-2026-23903Same product: Apache Shiro
CVE-2023-46750Same product: Apache Shiro
CVE-2026-49268Same product: Apache Shiro
CVE-2026-43827Same product: Apache Shiro
CVE-2023-46749Same product: Apache Shiro

Affected Assets

apache
shiro
≤ 2.0.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

SC-13 Cryptographic Protection partial match

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

References