Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

nvd логотип

CVE-2026-23901

Опубликовано: 10 фев. 2026
Источник: nvd
CVSS3: 2.5
EPSS Низкий

Описание

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.

Ссылки

Уязвимые конфигурации

Конфигурация 1
cpe:2.3:a:apache:shiro:*:*:*:*:*:*:*:*
Версия до 2.0.7 (исключая)

EPSS

Процентиль: 1%
0.00009
Низкий

2.5 Low

CVSS3

Дефекты

CWE-208

Связанные уязвимости

CVSS3: 2.5
ubuntu
около 2 месяцев назад

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.

CVSS3: 2.9
redhat
около 2 месяцев назад

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.

CVSS3: 2.5
debian
около 2 месяцев назад

Observable Timing Discrepancy vulnerability in Apache Shiro. This iss ...

github
около 2 месяцев назад

Apache Shiro Affected by an Observable Timing Discrepancy Vulnerability

EPSS

Процентиль: 1%
0.00009
Низкий

2.5 Low

CVSS3

Дефекты

CWE-208