Source Package: shiro (1.3.2-6)
Apache Shiro - Java Security Framework
The following binary packages are built from this source package:
- libshiro-java
Apache Shiro - Java Security Framework

Packages / Debian 13 (Trixie) / Source / java / shiro
Apache Shiro - Java Security Framework
Matching against OpenFactory catalog package versions is in progress.
| CVE | Severity | Version impact |
|---|---|---|
| [CVE-2026-58301] Published: When Apache Shiro is used with the Jakarta EE integration module, a low-privileged user can craft an HTTP request that causes the server to initiate a connection to an attacker-controlled URL and tran | Medium(5.9) | AffectedDetails (2)
|
| [CVE-2026-56091] Published: When using Apache Shiro with the shiro-guice module in a web servlet context, a specially crafted HTTP request may cause an authentication bypass. This vulnerability is similar to https://www.cve.org | High(8.2) | AffectedDetails (2)
|
| [CVE-2026-56130] Published: "Remember me" cookie age is not verified on the server. This potentially allows an attacker to intercept a valid cookie and reuse it indefinitely, even after the configured expiration time has passed. | Low(3) | AffectedDetails (2)
|
| [CVE-2026-49268] Published: A remote attacker can inject LDAP special characters into the Distinguished Name (DN) construction in DefaultLdapRealm class. User-supplied username input is directly concatenated into the LDAP DN tem | High(8.8) | AffectedDetails (2)
|
| [CVE-2026-43828] Published: Default configurations of Apache Shiro send sensitive cookies in HTTPS session without 'Secure' attribute. This issue affects Apache Shiro from 1.0 to 2.1.0, and 3.0.0-alpha-1. Users are recommend | Medium(6.5) | AffectedDetails (2)
|
| [CVE-2026-43827] Published: Default configurations of Apache Shiro have a session fixation vulnerability. This issue affects Apache Shiro from 1.0 to 2.1.0, and 3.0.0-alpha-1. Users are recommended to upgrade to version 2.1.1, | High(7.1) | AffectedDetails (2)
|
| [CVE-2026-23901] Published: shiro: CVE-2026-23901 | Low(2.9) | AffectedDetails (2)
|
| [CVE-2026-23903] Published: shiro: CVE-2026-23903 | Medium(5.3) | AffectedDetails (2)
|
| [CVE-2021-41303] Published: shiro: CVE-2021-41303 | Medium | AffectedDetails (2)
|
| [CVE-2019-12422] Published: shiro: CVE-2019-12422 | High(7.4) | AffectedDetails (2)
|
| CVE | Severity | Version impact |
|---|---|---|
| [CVE-2020-17510] Published: shiro: CVE-2020-17510 | Critical(9.8) | FixedDetails (2)
|
| [CVE-2020-13933] Published: shiro: CVE-2020-13933 | High(7.5) | FixedDetails (2)
|
| [CVE-2020-11989] Published: shiro: CVE-2020-11989 | Critical(9.8) | FixedDetails (2)
|
| [CVE-2020-1957] Published: shiro: CVE-2020-1957 | Medium | FixedDetails (2)
|
| [CVE-2016-6802] Published: Apache Shiro vulnerabilities | Medium(5.6) | FixedDetails (2)
|
| [CVE-2016-4437] Published: shiro: CVE-2016-4437 | High(7.3) CISA KEV | FixedDetails (2)
|
| [CVE-2014-0074] Published: shiro: CVE-2014-0074 | Medium | FixedDetails (2)
|
Last synced:
Authoritative source; repository metadata signature verified
trixie-main-amd64:3ab4e811cf4f3e5a335d382c58cc19d85f1abe7a4ef4689160ca1f637fa0e9b3
Authoritative source; repository metadata signature verified
trixie-main-arm64:753da751bbc7a679f48bd1b623ffd4479cb6861c426118284c76eb82909e4908