Is org.apache.shiro:shiro-core 2.2 vulnerable?

Maven · 2 releases from 2.2.0 to 2.2.1 · latest org.apache.shiro:shiro-core is 3.0.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. org.apache.shiro:shiro-core 2.2.1, the last 2.2 release, is affected by 1 known security advisory (1 low), including CVE-2026-56130. 1 more affects earlier 2.2.x releases. Upgrade to 3.0.0 or later to fix all of them.

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

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

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-core 2.2.1

  • LowCVE-2026-56130GHSA-m8g6-vrr2-x7ff25 Jun 2026

    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

Fixed within 2.2.x, affecting earlier releases

  • HighCVE-2026-49268GHSA-x96m-rh44-vgv817 Jun 2026

    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

Every org.apache.shiro:shiro-core 2.2.x release

Affected: 2.2.0 to 2.2.1. Latest org.apache.shiro:shiro-core: 3.0.2.

VersionKnown advisories
org.apache.shiro:shiro-core 2.2.1CVE-2026-56130
org.apache.shiro:shiro-core 2.2.0CVE-2026-56130, CVE-2026-49268

Which of your client projects are still on org.apache.shiro:shiro-core 2.2?

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

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.