Is org.springframework.data:spring-data-commons 3.2 vulnerable?

Maven · 13 releases from 3.2.0 to 3.2.12 · latest org.springframework.data:spring-data-commons is 4.1.2 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.springframework.data:spring-data-commons 3.2.12, the last 3.2 release, is affected by 2 known security advisories (2 medium), including CVE-2026-41721, CVE-2026-41711. Upgrade to 3.5.12 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.springframework.data:spring-data-commons -DdepVersion=3.5.12 -DforceVersion=true

Is your project on an affected org.springframework.data:spring-data-commons?

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.data:spring-data-commons 3.2.12

  • MediumCVE-2026-41721GHSA-5m4m-73w9-843310 Jun 2026

    Spring Data Commons: Denial of Service via excessive memory allocation in projection binding

    Affected
    >=4.0.0 <4.0.6 · >=3.5.0 <3.5.12 · >=3.4.0 <=3.4.14 · >=3.0.0 <=3.3.16 · <=2.7.19
    Fixed in
    3.5.12, 4.0.6
  • MediumCVE-2026-41711GHSA-5vpf-xvv7-c8vh10 Jun 2026

    Spring Data Commons: StackOverflowException when parsing Sort parameters (DoS)

    Affected
    >=4.0.0 <4.0.6 · >=3.5.0 <3.5.12 · >=3.4.0 <=3.4.14 · >=3.0.0 <=3.3.16 · <=2.7.19
    Fixed in
    3.5.12, 4.0.6

Every org.springframework.data:spring-data-commons 3.2.x release

Affected: 3.2.0 to 3.2.12. Latest org.springframework.data:spring-data-commons: 4.1.2.

VersionKnown advisories
org.springframework.data:spring-data-commons 3.2.12CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.11CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.10CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.9CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.8CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.7CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.6CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.5CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.4CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.3CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.2CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.1CVE-2026-41721, CVE-2026-41711
org.springframework.data:spring-data-commons 3.2.0CVE-2026-41721, CVE-2026-41711

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

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

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