Is org.springframework:spring-core 3.2 vulnerable?

Maven · 19 releases from 3.2.0 to 3.2.18 · latest org.springframework:spring-core is 7.0.10 · checked 18 Nov 2026

Yes: 5 known advisories

Yes. org.springframework:spring-core 3.2.18, the last 3.2 release, is affected by 5 known security advisories (2 high, 2 medium, 1 low), including CVE-2016-5007, CVE-2018-1272, CVE-2018-1271. 2 more affect earlier 3.2.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 3.2.18

  • 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-2016-5007GHSA-8crv-49fr-2h6j17 Oct 2018

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

    Affected
    <4.3.1
    Fixed in
    4.3.1
  • HighCVE-2018-1272GHSA-4487-x383-qpph17 Oct 2018

    Possible privilege escalation in org.springframework:spring-core

    Affected
    <4.3.15 · >=5.0.0 <5.0.5
    Fixed in
    4.3.15, 5.0.5
  • MediumCVE-2018-1271GHSA-g8hw-794c-4j9g17 Oct 2018

    Path Traversal in org.springframework:spring-core

    Affected
    >=5.0.0 <5.0.5 · <4.3.15
    Fixed in
    4.3.15, 5.0.5
  • MediumCVE-2018-1257GHSA-rcpf-vj53-7h2m17 Oct 2018

    Denial of Service in org.springframework:spring-core

    Affected
    >=5.0.0 <5.0.6 · <4.3.17
    Fixed in
    4.3.17, 5.0.6

Fixed within 3.2.x, affecting earlier releases

  • MediumCVE-2014-3578GHSA-rhcg-rwhx-qj3j14 May 2022

    Improper Limitation of a Pathname to a Restricted Directory in Spring Framework

    Affected
    >=3.0.0 <3.2.9 · >=4.0.0 <4.0.5
    Fixed in
    3.2.9, 4.0.5
  • HighCVE-2015-5211GHSA-pgf9-h69p-pcgf17 Oct 2018

    Files or Directories Accessible to External Parties in org.springframework:spring-core

    Affected
    >=4.2.0 <4.2.2 · >=4.0.0 <4.1.8 · <3.2.15
    Fixed in
    3.2.15, 4.1.8, 4.2.2

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

Affected: 3.2.0 to 3.2.18. Latest org.springframework:spring-core: 7.0.10.

VersionKnown advisories
org.springframework:spring-core 3.2.18CVE-2026-41848, CVE-2016-5007, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.17CVE-2026-41848, CVE-2016-5007, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.16CVE-2026-41848, CVE-2016-5007, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.15CVE-2026-41848, CVE-2016-5007, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.14CVE-2026-41848, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.13CVE-2026-41848, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.12CVE-2026-41848, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.11CVE-2026-41848, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.10CVE-2026-41848, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.9CVE-2026-41848, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.8CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.7CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.6CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.5CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.4CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.3CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.2CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.1CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257
org.springframework:spring-core 3.2.0CVE-2026-41848, CVE-2014-3578, CVE-2016-5007, CVE-2015-5211, CVE-2018-1272, CVE-2018-1271, CVE-2018-1257

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

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.