Is org.springframework:spring-core 6.0 vulnerable?
Maven · 24 releases from 6.0.0 to 6.0.23 · latest org.springframework:spring-core is 7.0.10 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. org.springframework:spring-core 6.0.23, the last 6.0 release, is affected by 1 known security advisory (1 high), including CVE-2025-41249. 1 more affects earlier 6.0.x releases. Upgrade to 6.2.11 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=6.2.11 -DforceVersion=trueIs your project on an affected org.springframework:spring-core?
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 6.0.23
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 6.0.x, affecting earlier releases
Spring Framework server Web DoS Vulnerability
- Affected
- >=6.1.2 <6.1.3 · >=6.0.15 <6.0.16
- Fixed in
- 6.0.16, 6.1.3
Every org.springframework:spring-core 6.0.x release
Affected: 6.0.0 to 6.0.23. Latest org.springframework:spring-core: 7.0.10.
| Version | Known advisories |
|---|---|
| org.springframework:spring-core 6.0.23 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.22 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.21 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.20 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.19 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.18 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.17 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.16 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.15 | CVE-2025-41249, CVE-2024-22233 |
| org.springframework:spring-core 6.0.14 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.13 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.12 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.11 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.10 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.9 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.8 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.7 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.6 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.5 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.4 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.3 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.2 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.1 | CVE-2025-41249 |
| org.springframework:spring-core 6.0.0 | CVE-2025-41249 |
Which of your client projects are still on org.springframework:spring-core 6.0?
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.