Is org.springframework:spring-core 5.3 vulnerable?

Maven · 40 releases from 5.3.0 to 5.3.39 · latest org.springframework:spring-core is 7.0.10 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.springframework:spring-core 5.3.39, the last 5.3 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2025-41249, CVE-2026-41848. 2 more affect earlier 5.3.x releases. Upgrade to 6.2.19 or later to fix all of them.

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

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

  • LowCVE-2026-41848GHSA-659m-px2c-25wj9 Jun 2026

    Spring Framework Denial of Service via AntPathMatcher

    Affected
    >=7.0.0 <7.0.8 · >=6.2.0 <6.2.19 · >=6.1.0 <=6.1.21 · <=5.3.39
    Fixed in
    6.2.19, 7.0.8
  • HighCVE-2025-41249GHSA-jmp9-x22r-554x16 Sept 2025

    Spring Framework annotation detection mechanism may result in improper authorization

    Affected
    >=5.3.0 <=5.3.44 · >=6.0.0 <=6.1.22 · >=6.2.0 <6.2.11
    Fixed in
    6.2.11

Fixed within 5.3.x, affecting earlier releases

  • MediumCVE-2021-22096GHSA-rfmp-97jj-h8m624 May 2022

    Improper Output Neutralization for Logs in Spring Framework

    Affected
    >=5.3.0 <5.3.11 · >=5.2.0 <5.2.18
    Fixed in
    5.2.18, 5.3.11
  • MediumCVE-2021-22060GHSA-6gf2-pvqw-37ph12 Jan 2022

    Log entry injection in Spring Framework

    Affected
    >=5.3.0 <5.3.14 · >=5.2.0 <5.2.19
    Fixed in
    5.2.19, 5.3.14

Every org.springframework:spring-core 5.3.x release

Affected: 5.3.0 to 5.3.39. Latest org.springframework:spring-core: 7.0.10.

VersionKnown advisories
org.springframework:spring-core 5.3.39CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.38CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.37CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.36CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.35CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.34CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.33CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.32CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.31CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.30CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.29CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.28CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.27CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.26CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.25CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.24CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.23CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.22CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.21CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.20CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.19CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.18CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.17CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.16CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.15CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.14CVE-2026-41848, CVE-2025-41249
org.springframework:spring-core 5.3.13CVE-2026-41848, CVE-2025-41249, CVE-2021-22060
org.springframework:spring-core 5.3.12CVE-2026-41848, CVE-2025-41249, CVE-2021-22060
org.springframework:spring-core 5.3.11CVE-2026-41848, CVE-2025-41249, CVE-2021-22060
org.springframework:spring-core 5.3.10CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.9CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.8CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.7CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.6CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.5CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.4CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.3CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.2CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.1CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060
org.springframework:spring-core 5.3.0CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060

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

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

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