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.
mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=6.2.19 -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 5.3.39
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
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
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
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.
| Version | Known advisories |
|---|---|
| org.springframework:spring-core 5.3.39 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.38 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.37 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.36 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.35 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.34 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.33 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.32 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.31 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.30 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.29 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.28 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.27 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.26 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.25 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.24 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.23 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.22 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.21 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.20 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.19 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.18 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.17 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.16 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.15 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.14 | CVE-2026-41848, CVE-2025-41249 |
| org.springframework:spring-core 5.3.13 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22060 |
| org.springframework:spring-core 5.3.12 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22060 |
| org.springframework:spring-core 5.3.11 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22060 |
| org.springframework:spring-core 5.3.10 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.9 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.8 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.7 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.6 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.5 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.4 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.3 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.2 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.1 | CVE-2026-41848, CVE-2025-41249, CVE-2021-22096, CVE-2021-22060 |
| org.springframework:spring-core 5.3.0 | CVE-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.