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

Maven · 12 releases from 6.5.0 to 6.5.11 · latest org.springframework.security:spring-security-core is 7.1.2 · checked 18 Nov 2026

No known advisories in the last release

org.springframework.security:spring-security-core 6.5.11, the last 6.5 release, has no known advisories. 3 advisories affect earlier 6.5.x releases, so update to 6.5.11.

Update within 6.5:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.5.11 -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

Fixed within 6.5.x, affecting earlier releases

  • LowCVE-2026-22746GHSA-vxf7-qj7q-83fh22 Apr 2026

    Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider

    Affected
    >=5.7.0 <=5.7.22 · >=5.8.0 <=5.8.24 · >=6.3.0 <=6.3.15 · >=6.4.0 <=6.4.15 · >=6.5.0 <6.5.10 · >=7.0.0 <7.0.5
    Fixed in
    6.5.10, 7.0.5
  • MediumCVE-2026-22751GHSA-x2wq-9x2f-fhj721 Apr 2026

    Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured

    Affected
    >=6.5.0 <6.5.10 · >=7.0.3 <7.0.5 · >=6.4.0 <=6.4.13
    Fixed in
    6.5.10, 7.0.5
  • HighCVE-2025-41248GHSA-8v5q-rhf3-jphm16 Sept 2025

    Spring Security annotation detection mechanism has authorization bypass

    Affected
    >=6.4.0 <6.4.10 · >=6.5.0 <6.5.4
    Fixed in
    6.4.10, 6.5.4

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

Affected: 6.5.0 to 6.5.9. 6.5.10 and later are not affected. Latest org.springframework.security:spring-security-core: 7.1.2.

VersionKnown advisories
org.springframework.security:spring-security-core 6.5.11None
org.springframework.security:spring-security-core 6.5.10None
org.springframework.security:spring-security-core 6.5.9CVE-2026-22746, CVE-2026-22751
org.springframework.security:spring-security-core 6.5.8CVE-2026-22746, CVE-2026-22751
org.springframework.security:spring-security-core 6.5.7CVE-2026-22746, CVE-2026-22751
org.springframework.security:spring-security-core 6.5.6CVE-2026-22746, CVE-2026-22751
org.springframework.security:spring-security-core 6.5.5CVE-2026-22746, CVE-2026-22751
org.springframework.security:spring-security-core 6.5.4CVE-2026-22746, CVE-2026-22751
org.springframework.security:spring-security-core 6.5.3CVE-2026-22746, CVE-2026-22751, CVE-2025-41248
org.springframework.security:spring-security-core 6.5.2CVE-2026-22746, CVE-2026-22751, CVE-2025-41248
org.springframework.security:spring-security-core 6.5.1CVE-2026-22746, CVE-2026-22751, CVE-2025-41248
org.springframework.security:spring-security-core 6.5.0CVE-2026-22746, CVE-2026-22751, CVE-2025-41248

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

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.