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

Maven · 7 releases from 2.0.0 to 2.0.6 · latest org.apache.shiro:shiro-spring is 3.0.2 · checked 20 Nov 2026

Yes: 1 known advisory

Yes. org.apache.shiro:shiro-spring 2.0.6, the last 2.0 release, is affected by 1 known security advisory (1 medium), including 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 2.0.6

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

    Apache Shiro has an Authentication Bypass

    Affected
    <2.1.0
    Fixed in
    2.1.0

Every org.apache.shiro:shiro-spring 2.0.x release

Affected: 2.0.0 to 2.0.6. Latest org.apache.shiro:shiro-spring: 3.0.2.

VersionKnown advisories
org.apache.shiro:shiro-spring 2.0.6CVE-2026-23903
org.apache.shiro:shiro-spring 2.0.5CVE-2026-23903
org.apache.shiro:shiro-spring 2.0.4CVE-2026-23903
org.apache.shiro:shiro-spring 2.0.3CVE-2026-23903
org.apache.shiro:shiro-spring 2.0.2CVE-2026-23903
org.apache.shiro:shiro-spring 2.0.1CVE-2026-23903
org.apache.shiro:shiro-spring 2.0.0CVE-2026-23903

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

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.