Is org.apache.shiro:shiro-core 1.3 vulnerable?
Maven · 3 releases from 1.3.0 to 1.3.2 · latest org.apache.shiro:shiro-core is 3.0.2 · checked 18 Nov 2026
Yes: 12 known advisories
Yes. org.apache.shiro:shiro-core 1.3.2, the last 1.3 release, is affected by 12 known security advisories (5 critical, 3 high, 2 medium, 2 low), including CVE-2022-40664, CVE-2022-32532, CVE-2021-41303. Upgrade to 3.0.0 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.apache.shiro:shiro-core -DdepVersion=3.0.0 -DforceVersion=trueIs your project on an affected org.apache.shiro:shiro-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.apache.shiro:shiro-core 1.3.2
Apache Shiro's "remember me" cookie age is not verified on the server.
- Affected
- >=1.2.4 <3.0.0
- Fixed in
- 3.0.0
Apache Shiro: LDAP DN Injection in DefaultLdapRealm
- Affected
- <2.2.1 · >=3.0.0-alpha-0 <3.0.0-alpha-2
- Fixed in
- 2.2.1, 3.0.0-alpha-2
Apache Shiro has a session fixation vulnerability
- Affected
- >=1.0.0-incubating <2.2.0 · >=3.0.0-alpha-1 <3.0.0-alpha-2
- Fixed in
- 2.2.0, 3.0.0-alpha-2
Apache Shiro Affected by an Observable Timing Discrepancy Vulnerability
- Affected
- <2.1.0
- Fixed in
- 2.1.0
Apache Shiro vulnerable to path traversal
- Affected
- <1.13.0 · >=2.0.0alpha1 <2.0.0-alpha4
- Fixed in
- 1.13.0, 2.0.0-alpha4
Apache Shiro Authentication Bypass vulnerability
- Affected
- <1.10.0
- Fixed in
- 1.10.0
Improper Authorization in Apache Shiro
- Affected
- <1.9.1
- Fixed in
- 1.9.1
Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass
- Affected
- <1.8.0
- Fixed in
- 1.8.0
Authentication bypass in Apache Shiro
- Affected
- <1.6.0
- Fixed in
- 1.6.0
Improper Authentication in Apache Shiro
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Improper Authentication in Apache Shiro
- Affected
- <1.5.3
- Fixed in
- 1.5.3
Improper input validation in Apache Shiro
- Affected
- <1.4.2
- Fixed in
- 1.4.2
Every org.apache.shiro:shiro-core 1.3.x release
Affected: 1.3.0 to 1.3.2. Latest org.apache.shiro:shiro-core: 3.0.2.
| Version | Known advisories |
|---|---|
| org.apache.shiro:shiro-core 1.3.2 | CVE-2026-56130, CVE-2026-49268, CVE-2026-43827, CVE-2026-23901, CVE-2023-46749, CVE-2022-40664, CVE-2022-32532, CVE-2021-41303, CVE-2020-13933, CVE-2020-1957, CVE-2020-11989, CVE-2019-12422 |
| org.apache.shiro:shiro-core 1.3.1 | CVE-2026-56130, CVE-2026-49268, CVE-2026-43827, CVE-2026-23901, CVE-2023-46749, CVE-2022-40664, CVE-2022-32532, CVE-2021-41303, CVE-2020-13933, CVE-2020-1957, CVE-2020-11989, CVE-2019-12422 |
| org.apache.shiro:shiro-core 1.3.0 | CVE-2026-56130, CVE-2026-49268, CVE-2026-43827, CVE-2026-23901, CVE-2023-46749, CVE-2022-40664, CVE-2022-32532, CVE-2021-41303, CVE-2020-13933, CVE-2020-1957, CVE-2020-11989, CVE-2019-12422 |
Which of your client projects are still on org.apache.shiro:shiro-core 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.shiro:shiro-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.shiro:shiro-core versions
- org.apache.shiro:shiro-core 1.6
- org.apache.shiro:shiro-core 1.5
- org.apache.shiro:shiro-core 1.4
- org.apache.shiro:shiro-core 1.2
- org.apache.shiro:shiro-core 1.1
- org.apache.shiro:shiro-core 3.0
- org.apache.shiro:shiro-core 2.2
- org.apache.shiro:shiro-core 2.1
- org.apache.shiro:shiro-core 2.0
- org.apache.shiro:shiro-core 1.13
- org.apache.shiro:shiro-core 1.12
- org.apache.shiro:shiro-core 1.11
- All org.apache.shiro:shiro-core advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.