Is org.springframework:spring-beans 5.2 vulnerable?

Maven · 26 releases from 5.2.0 to 5.2.25 · latest org.springframework:spring-beans is 7.0.10 · checked 18 Nov 2026

No known advisories in the last release

org.springframework:spring-beans 5.2.25, the last 5.2 release, has no known advisories. 2 advisories affect earlier 5.2.x releases, so update to 5.2.25.

Update within 5.2:mvn versions:use-dep-version -Dincludes=org.springframework:spring-beans -DdepVersion=5.2.25 -DforceVersion=true

Is your project on an affected org.springframework:spring-beans?

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

Fixed within 5.2.x, affecting earlier releases

  • HighCVE-2022-22970GHSA-hh26-6xwr-ggv713 May 2022

    Denial of service in Spring Framework

    Affected
    <5.2.22.RELEASE · >=5.3.0 <5.3.20
    Fixed in
    5.2.22.RELEASE, 5.3.20
  • CriticalCVE-2022-22965GHSA-36p3-wjmg-h94x31 Mar 2022

    Remote Code Execution in Spring Framework

    Affected
    <5.2.20.RELEASE · >=5.3.0 <5.3.18
    Fixed in
    5.2.20.RELEASE, 5.3.18

Every org.springframework:spring-beans 5.2.x release

Affected: 5.2.0 to 5.2.21. 5.2.22 and later are not affected. Latest org.springframework:spring-beans: 7.0.10.

VersionKnown advisories
org.springframework:spring-beans 5.2.25None
org.springframework:spring-beans 5.2.24None
org.springframework:spring-beans 5.2.23None
org.springframework:spring-beans 5.2.22None
org.springframework:spring-beans 5.2.21CVE-2022-22970
org.springframework:spring-beans 5.2.20CVE-2022-22970
org.springframework:spring-beans 5.2.19CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.18CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.17CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.16CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.15CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.14CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.13CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.12CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.11CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.10CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.9CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.8CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.7CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.6CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.5CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.4CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.3CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.2CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.1CVE-2022-22970, CVE-2022-22965
org.springframework:spring-beans 5.2.0CVE-2022-22970, CVE-2022-22965

Which of your client projects are still on org.springframework:spring-beans 5.2?

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

Other org.springframework:spring-beans 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.