Is org.springframework.security:spring-security-core 3.2 vulnerable?

Maven · 11 releases from 3.2.0 to 3.2.10 · latest org.springframework.security:spring-security-core is 7.1.2 · checked 18 Nov 2026

Yes: 6 known advisories

Yes. org.springframework.security:spring-security-core 3.2.10, the last 3.2 release, is affected by 6 known security advisories (1 critical, 3 high, 2 medium), including CVE-2022-22978, CVE-2024-22257, CVE-2019-11272. 3 more affect earlier 3.2.x releases. Upgrade to 5.7.14 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=5.7.14 -DforceVersion=true

Is your project on an affected org.springframework.security:spring-security-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.springframework.security:spring-security-core 3.2.10

  • MediumCVE-2024-38827GHSA-q3v6-hm2v-pw992 Dec 2024

    Spring Framework has Authorization Bypass for Case Sensitive Comparisons

    Affected
    <5.7.14 · >=5.8.0 <5.8.16 · >=6.0.0 <6.0.14 · >=6.1.0 <6.1.12 · >=6.2.0 <6.2.8 · >=6.3.0 <6.3.5
    Fixed in
    5.7.14, 5.8.16, 6.0.14, 6.1.12, 6.2.8, 6.3.5
  • HighCVE-2024-22257GHSA-f3jh-qvm4-mg3918 Mar 2024

    Erroneous authentication pass in Spring Security

    Affected
    <5.7.12 · >=5.8.0 <5.8.11 · >=6.0.0 <6.1.8 · >=6.2.0 <6.2.3
    Fixed in
    5.7.12, 5.8.11, 6.1.8, 6.2.3
  • CriticalCVE-2022-22978GHSA-hh32-7344-cg2f20 May 2022

    Authorization bypass in Spring Security

    Affected
    >=5.5.0 <5.5.7 · >=5.6.0 <5.6.4 · <5.4.11
    Fixed in
    5.4.11, 5.5.7, 5.6.4
  • MediumCVE-2020-5408GHSA-2ppp-9496-p23q15 Jun 2020

    Insufficient Entropy in Spring Security

    Affected
    >=5.3.0 <5.3.2 · >=5.2.0 <5.2.4 · >=5.1.0 <5.1.10 · >=5.0.0 <5.0.16 · <4.2.16
    Fixed in
    4.2.16, 5.0.16, 5.1.10, 5.2.4, 5.3.2
  • HighCVE-2019-11272GHSA-v33x-prhc-gph527 Jun 2019

    Insufficiently Protected Credentials and Improper Authentication in Spring Security

    Affected
    <4.2.13
    Fixed in
    4.2.13
  • HighCVE-2016-5007GHSA-8crv-49fr-2h6j17 Oct 2018

    Spring Security and Spring Framework may not recognize certain paths that should be protected

    Affected
    <4.1.1
    Fixed in
    4.1.1

Fixed within 3.2.x, affecting earlier releases

  • HighCVE-2014-0097GHSA-gv9v-c375-hvmg13 May 2022

    Improper Authentication in Spring Security

    Affected
    >=3.2.0 <3.2.2.RELEASE · >=3.1.0 <3.1.5.RELEASE
    Fixed in
    3.1.5.RELEASE, 3.2.2.RELEASE
  • HighCVE-2016-9879GHSA-v35c-49j6-q8hq15 Sept 2020

    Security Constraint Bypass in Spring Security

    Affected
    <3.2.10.RELEASE · >=4.0.0.RELEASE <4.1.4.RELEASE · >=4.2.0.RELEASE <4.2.1.RELEASE
    Fixed in
    3.2.10.RELEASE, 4.1.4.RELEASE, 4.2.1.RELEASE
  • CriticalCVE-2014-3527GHSA-wmv4-5w76-vp9g15 Sept 2020

    Authorization Bypass in Spring Security

    Affected
    <3.1.7 · >=3.2.0 <3.2.5
    Fixed in
    3.1.7, 3.2.5

Every org.springframework.security:spring-security-core 3.2.x release

Affected: 3.2.0 to 3.2.10. Latest org.springframework.security:spring-security-core: 7.1.2.

VersionKnown advisories
org.springframework.security:spring-security-core 3.2.10CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.9CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.8CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.7CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.6CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.5CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.4CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.3CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.2CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.1CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007
org.springframework.security:spring-security-core 3.2.0CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007

Which of your client projects are still on org.springframework.security:spring-security-core 3.2?

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

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