Is org.apache.shiro:shiro-spring 1.6 vulnerable?

Maven · 1 release from 1.6.0 to 1.6.0 · latest org.apache.shiro:shiro-spring is 3.0.2 · checked 20 Nov 2026

Yes: 3 known advisories

Yes. org.apache.shiro:shiro-spring 1.6.0, the last 1.6 release, is affected by 3 known security advisories (2 critical, 1 medium), including CVE-2020-17523, CVE-2020-17510, CVE-2026-23903. Upgrade to 2.1.0 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.shiro:shiro-spring -DdepVersion=2.1.0 -DforceVersion=true

Is your project on an affected org.apache.shiro:shiro-spring?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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-spring 1.6.0

  • MediumCVE-2026-23903GHSA-c244-p6m5-vqj69 Feb 2026

    Apache Shiro has an Authentication Bypass

    Affected
    <2.1.0
    Fixed in
    2.1.0
  • CriticalCVE-2020-17523GHSA-v98j-7crc-wvrj9 Feb 2022

    Authentication bypass in Apache Shiro

    Affected
    <1.7.1
    Fixed in
    1.7.1
  • CriticalCVE-2020-17510GHSA-7cj4-gj8m-m2f722 Apr 2021

    Authentication bypass in Apache Shiro

    Affected
    <1.7.0
    Fixed in
    1.7.0

Which of your client projects are still on org.apache.shiro:shiro-spring 1.6?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.shiro:shiro-spring version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.apache.shiro:shiro-spring versions

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.