VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.shiro:shiro-web: vulnerability history, versions and safety

org.apache.shiro:shiro-web is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 43 releases, from Feb 2022 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 26 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.shiro:shiro-web vulnerabilities

Vulert verdict on org.apache.shiro:shiro-web 3.0.1 i

Updated on 23 Oct 2026

Good news: 3.0.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 3.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.0.1 — unaffected i
  • Vulnerabilities on record 4 over 4 years · 1 in the last year i
  • Latest disclosure 26 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 25 packages i
  • Stars 4,461 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.shiro:shiro-web, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.0.1 23 Aug 2026 none Apache-2.0 — Details →
3.0.0 20 Jun 2026 none Apache-2.0 — Details →
2.2.1 14 Jun 2026 none Apache-2.0 — Details →
2.2.0 14 May 2026 none Apache-2.0 — Details →
3.0.0-alpha-1 23 Feb 2026 none Apache-2.0 — Details →
2.1.0 04 Feb 2026 M1 Apache-2.0 Yes Details →
2.0.6 02 Nov 2025 M1 Apache-2.0 Yes Details →
2.0.5 01 Jul 2025 M1 Apache-2.0 Yes Details →
2.0.4 17 Apr 2025 M1 Apache-2.0 Yes Details →
2.0.3 05 Apr 2025 M1 Apache-2.0 Yes Details →
2.0.2 07 Nov 2024 M1 Apache-2.0 Yes Details →
2.0.1 25 May 2024 M1 Apache-2.0 Yes Details →
2.0.0 20 Feb 2024 M1 Apache-2.0 Yes Details →
2.0.0-alpha-4 07 Nov 2023 M1 Apache-2.0 Yes Details →
1.13.0 31 Oct 2023 M1 Apache-2.0 Yes Details →
2.0.0-alpha-3 25 Jul 2023 M1 Apache-2.0 Yes Details →
1.12.0 11 Jul 2023 M2 Apache-2.0 Yes Details →
2.0.0-alpha-2 04 May 2023 M1 Apache-2.0 Yes Details →
2.0.0-alpha-1 28 Feb 2023 M1 Apache-2.0 Yes Details →
1.11.0 08 Jan 2023 C1 M2 Apache-2.0 Yes Details →
1.10.1 14 Nov 2022 C1 M2 Apache-2.0 Yes Details →
1.10.0 07 Oct 2022 C1 M2 Apache-2.0 Yes Details →
1.9.1 23 Jun 2022 C1 M2 Apache-2.0 Yes Details →
1.9.0 16 Mar 2022 C1 M2 Apache-2.0 Yes Details →
1.8.0 23 Aug 2021 C1 M2 Apache-2.0 Yes Details →
1.7.1 27 Jan 2021 C1 M2 Apache-2.0 Yes Details →
1.7.0 23 Oct 2020 C2 M2 Apache-2.0 Yes Details →
1.6.0 11 Aug 2020 C2 M2 Apache-2.0 Yes Details →
1.5.3 26 Apr 2020 C2 M2 Apache-2.0 Yes Details →
1.5.2 18 Mar 2020 C2 M2 Apache-2.0 Yes Details →
1.5.1 17 Feb 2020 C2 M2 Apache-2.0 Yes Details →
1.5.0 21 Jan 2020 C2 M2 Apache-2.0 Yes Details →
1.4.2 08 Nov 2019 C2 M2 Apache-2.0 Yes Details →
1.4.1 18 Apr 2019 C2 M2 Apache-2.0 Yes Details →
1.4.0 05 May 2017 C2 M2 Apache-2.0 Yes Details →
1.4.0-RC2 10 Nov 2016 C2 M2 Apache-2.0 Yes Details →
1.3.2 09 Sep 2016 C2 M2 Apache-2.0 Yes Details →
1.3.1 19 Aug 2016 C2 M2 Apache-2.0 Yes Details →
1.3.0 22 Jul 2016 C2 M2 Apache-2.0 Yes Details →
1.2.6 28 Jun 2016 C2 M2 Apache-2.0 Yes Details →
1.2.5 19 May 2016 C2 M2 Apache-2.0 Yes Details →
1.2.4 08 Jul 2015 C2 M2 Apache-2.0 Yes Details →
1.2.3 25 Feb 2014 C2 M2 Apache-2.0 Yes Details →
1.2.2 11 May 2013 C2 M2 Apache-2.0 Yes Details →
1.2.1 25 Jul 2012 C2 M2 Apache-2.0 Yes Details →
1.2.0 20 Jan 2012 C2 M2 Apache-2.0 Yes Details →
1.1.0 30 Oct 2010 C2 M2 Apache-2.0 Yes Details →
1.0.0-incubating 21 May 2010 C2 M2 Apache-2.0 Yes Details →

All 48 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.shiro:shiro-web

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-17523: Authentication bypass in Apache Shiro 9.8 critical 1.7.1 09 Feb 2022
CVE-2023-34478: Path Traversal in Apache Shiro 9.8 critical 1.12.0 24 Jul 2023
CVE-2023-46750: Open redirect in Apache Shiro 6.1 medium 1.13.0 14 Dec 2023
CVE-2026-43828: Apache Shiro Sensitive Cookie Transmission Vulnerability 5.9 medium 2.2.0 26 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.shiro:shiro-web

Is org.apache.shiro:shiro-web safe to use?

Vulert records 4 vulnerabilities for org.apache.shiro:shiro-web in Maven: 2 critical, 0 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.shiro:shiro-web's Vulert package health score?

Vulert scores org.apache.shiro:shiro-web 81/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.shiro:shiro-web affected?

No. 3.0.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.shiro:shiro-web should I use?

3.0.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.shiro:shiro-web have?

4 vulnerabilities are recorded for org.apache.shiro:shiro-web in the Maven ecosystem: 2 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.shiro:shiro-web vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.shiro:shiro-web in the last 12 months, and the oldest entry in this database dates to 09 Feb 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.shiro:shiro-web are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.shiro:shiro-web for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.shiro:shiro-web version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.