Is org.springframework:spring-context 6.1 vulnerable?

Maven · 22 releases from 6.1.0 to 6.1.21 · latest org.springframework:spring-context is 7.0.10 · checked 18 Nov 2026

No known advisories in the last release

org.springframework:spring-context 6.1.21, the last 6.1 release, has no known advisories. 2 advisories affect earlier 6.1.x releases, so update to 6.1.21.

Update within 6.1:mvn versions:use-dep-version -Dincludes=org.springframework:spring-context -DdepVersion=6.1.21 -DforceVersion=true

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

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.1.x, affecting earlier releases

  • LowCVE-2025-22233GHSA-4wp7-92pw-q26416 May 2025

    Spring Framework DataBinder Case Sensitive Match Exception

    Affected
    >=6.2.0 <6.2.7 · >=6.1.0 <6.1.20 · >=6.0.0 <=6.0.23 · <=5.3.39
    Fixed in
    6.1.20, 6.2.7
  • MediumCVE-2024-38820GHSA-4gc7-5j7h-4qph18 Oct 2024

    Spring Framework DataBinder Case Sensitive Match Exception

    Affected
    >=6.1.0 <6.1.14 · >=6.0.0 <=6.0.24 · <=5.3.40
    Fixed in
    6.1.14

Every org.springframework:spring-context 6.1.x release

Affected: 6.1.0 to 6.1.19. 6.1.20 and later are not affected. Latest org.springframework:spring-context: 7.0.10.

VersionKnown advisories
org.springframework:spring-context 6.1.21None
org.springframework:spring-context 6.1.20None
org.springframework:spring-context 6.1.19CVE-2025-22233
org.springframework:spring-context 6.1.18CVE-2025-22233
org.springframework:spring-context 6.1.17CVE-2025-22233
org.springframework:spring-context 6.1.16CVE-2025-22233
org.springframework:spring-context 6.1.15CVE-2025-22233
org.springframework:spring-context 6.1.14CVE-2025-22233
org.springframework:spring-context 6.1.13CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.12CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.11CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.10CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.9CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.8CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.7CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.6CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.5CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.4CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.3CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.2CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.1CVE-2025-22233, CVE-2024-38820
org.springframework:spring-context 6.1.0CVE-2025-22233, CVE-2024-38820

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

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

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