Is org.springframework.security:spring-security-core 3.1 vulnerable?
Maven · 8 releases from 3.1.0 to 3.1.7 · latest org.springframework.security:spring-security-core is 7.1.2 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. org.springframework.security:spring-security-core 3.1.7, the last 3.1 release, is affected by 7 known security advisories (1 critical, 4 high, 2 medium), including CVE-2022-22978, CVE-2024-22257, CVE-2016-9879. 3 more affect earlier 3.1.x releases. Upgrade to 5.7.14 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=5.7.14 -DforceVersion=trueIs your project on an affected org.springframework.security:spring-security-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.security:spring-security-core 3.1.7
Spring Framework has Authorization Bypass for Case Sensitive Comparisons
- Affected
- <5.7.14 · >=5.8.0 <5.8.16 · >=6.0.0 <6.0.14 · >=6.1.0 <6.1.12 · >=6.2.0 <6.2.8 · >=6.3.0 <6.3.5
- Fixed in
- 5.7.14, 5.8.16, 6.0.14, 6.1.12, 6.2.8, 6.3.5
Erroneous authentication pass in Spring Security
- Affected
- <5.7.12 · >=5.8.0 <5.8.11 · >=6.0.0 <6.1.8 · >=6.2.0 <6.2.3
- Fixed in
- 5.7.12, 5.8.11, 6.1.8, 6.2.3
Authorization bypass in Spring Security
- Affected
- >=5.5.0 <5.5.7 · >=5.6.0 <5.6.4 · <5.4.11
- Fixed in
- 5.4.11, 5.5.7, 5.6.4
Security Constraint Bypass in Spring Security
- Affected
- <3.2.10.RELEASE · >=4.0.0.RELEASE <4.1.4.RELEASE · >=4.2.0.RELEASE <4.2.1.RELEASE
- Fixed in
- 3.2.10.RELEASE, 4.1.4.RELEASE, 4.2.1.RELEASE
Insufficient Entropy in Spring Security
- Affected
- >=5.3.0 <5.3.2 · >=5.2.0 <5.2.4 · >=5.1.0 <5.1.10 · >=5.0.0 <5.0.16 · <4.2.16
- Fixed in
- 4.2.16, 5.0.16, 5.1.10, 5.2.4, 5.3.2
Insufficiently Protected Credentials and Improper Authentication in Spring Security
- Affected
- <4.2.13
- Fixed in
- 4.2.13
Spring Security and Spring Framework may not recognize certain paths that should be protected
- Affected
- <4.1.1
- Fixed in
- 4.1.1
Fixed within 3.1.x, affecting earlier releases
Exposure of Sensitive Information to an Unauthorized Actor in Spring Security
- Affected
- <2.0.8 · >=3.0.0 <3.0.8 · >=3.1.0 <3.1.3
- Fixed in
- 2.0.8, 3.0.8, 3.1.3
Improper Authentication in Spring Security
- Affected
- >=3.2.0 <3.2.2.RELEASE · >=3.1.0 <3.1.5.RELEASE
- Fixed in
- 3.1.5.RELEASE, 3.2.2.RELEASE
Authorization Bypass in Spring Security
- Affected
- <3.1.7 · >=3.2.0 <3.2.5
- Fixed in
- 3.1.7, 3.2.5
Every org.springframework.security:spring-security-core 3.1.x release
Affected: 3.1.0 to 3.1.7. Latest org.springframework.security:spring-security-core: 7.1.2.
| Version | Known advisories |
|---|---|
| org.springframework.security:spring-security-core 3.1.7 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.6 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.5 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.4 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.3 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.2 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2012-5055, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.1 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2012-5055, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
| org.springframework.security:spring-security-core 3.1.0 | CVE-2024-38827, CVE-2024-22257, CVE-2022-22978, CVE-2012-5055, CVE-2014-0097, CVE-2016-9879, CVE-2014-3527, CVE-2020-5408, CVE-2019-11272, CVE-2016-5007 |
Which of your client projects are still on org.springframework.security:spring-security-core 3.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.springframework.security:spring-security-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.springframework.security:spring-security-core versions
- org.springframework.security:spring-security-core 4.1
- org.springframework.security:spring-security-core 4.0
- org.springframework.security:spring-security-core 3.2
- org.springframework.security:spring-security-core 3.0
- org.springframework.security:spring-security-core 2.0
- org.springframework.security:spring-security-core 7.1
- org.springframework.security:spring-security-core 7.0
- org.springframework.security:spring-security-core 6.5
- org.springframework.security:spring-security-core 6.4
- org.springframework.security:spring-security-core 6.3
- org.springframework.security:spring-security-core 6.2
- org.springframework.security:spring-security-core 6.1
- All org.springframework.security:spring-security-core advisories
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.