ubuntu-cve-2026-23901
Vulnerability from osv_ubuntu
Published
2026-02-10 10:15
Modified
2026-05-20 15:26
Summary
Details
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.
Severity
1.0 (Low)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.2.4-1ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.2.4-1ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.4-1",
"1.2.4-1ubuntu0.1~esm1",
"1.2.4-1ubuntu0.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.3.2-3ubuntu0.18.04.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.3.2-3ubuntu0.18.04.1~esm1?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.3.2-2",
"1.3.2-3~18.04",
"1.3.2-3~18.04.1",
"1.3.2-3ubuntu0.18.04.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.3.2-4ubuntu0.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.3.2-4ubuntu0.2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.3.2-4",
"1.3.2-4ubuntu0.1",
"1.3.2-4ubuntu0.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.3.2-5"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.3.2-5?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.3.2-4",
"1.3.2-5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.3.2-5ubuntu0.24.04.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.3.2-5ubuntu0.24.04.1~esm1?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.3.2-5",
"1.3.2-5ubuntu0.24.04.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.3.2-6ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.3.2-6ubuntu1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.3.2-6ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libshiro-java",
"binary_version": "1.3.2-6ubuntu2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "shiro",
"purl": "pkg:deb/ubuntu/shiro@1.3.2-6ubuntu2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.3.2-6ubuntu1",
"1.3.2-6ubuntu2"
]
}
],
"aliases": [],
"details": "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 \u00a0discusses this as well. Typically, brute force attack can be mitigated at the infrastructure level.",
"id": "UBUNTU-CVE-2026-23901",
"modified": "2026-05-20T15:26:04Z",
"published": "2026-02-10T10:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-23901"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23901"
},
{
"type": "REPORT",
"url": "https://www.openwall.com/lists/oss-security/2026/02/08/2"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/AU:Y/R:A/V:C/RE:L/U:Green",
"type": "CVSS_V4"
},
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-23901"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…