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

Maven · 10 releases from 6.1.0 to 6.1.9 · latest org.springframework.security:spring-security-core is 7.1.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. org.springframework.security:spring-security-core 6.1.9, the last 6.1 release, is affected by 1 known security advisory (1 medium), including CVE-2024-38827. 2 more affect earlier 6.1.x releases. Upgrade to 6.1.12 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.1.12 -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 6.1.9

  • 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

Fixed within 6.1.x, affecting earlier releases

  • 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
  • HighCVE-2024-22234GHSA-w3w6-26f2-p47420 Feb 2024

    Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

    Affected
    >=6.1.0 <6.1.7 · >=6.2.0 <6.2.2
    Fixed in
    6.1.7, 6.2.2

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

Affected: 6.1.0 to 6.1.9. Latest org.springframework.security:spring-security-core: 7.1.2.

VersionKnown advisories
org.springframework.security:spring-security-core 6.1.9CVE-2024-38827
org.springframework.security:spring-security-core 6.1.8CVE-2024-38827
org.springframework.security:spring-security-core 6.1.7CVE-2024-38827, CVE-2024-22257
org.springframework.security:spring-security-core 6.1.6CVE-2024-38827, CVE-2024-22257, CVE-2024-22234
org.springframework.security:spring-security-core 6.1.5CVE-2024-38827, CVE-2024-22257, CVE-2024-22234
org.springframework.security:spring-security-core 6.1.4CVE-2024-38827, CVE-2024-22257, CVE-2024-22234
org.springframework.security:spring-security-core 6.1.3CVE-2024-38827, CVE-2024-22257, CVE-2024-22234
org.springframework.security:spring-security-core 6.1.2CVE-2024-38827, CVE-2024-22257, CVE-2024-22234
org.springframework.security:spring-security-core 6.1.1CVE-2024-38827, CVE-2024-22257, CVE-2024-22234
org.springframework.security:spring-security-core 6.1.0CVE-2024-38827, CVE-2024-22257, CVE-2024-22234

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

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.