org.springframework.security:spring-security-core
Maven package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 7.0.5 | and later versions | 0C0H0M0L |
| 7.0.3 | up to 7.0.5 | 0C0H1M1L |
| 7.0.0 | up to 7.0.3 | 0C0H0M1L |
| 6.5.10 | up to 7.0.0 | 0C0H0M0L |
| 6.5.4 | up to 6.5.10 | 0C0H1M1L |
| 6.5.0 | up to 6.5.4 | 0C1H1M1L |
| after 6.4.15 | up to 6.5.0 | 0C0H0M0L |
| after 6.4.13 | up to 6.4.15 (included) | 0C0H0M1L |
| 6.4.10 | up to 6.4.13 (included) | 0C0H1M1L |
| 6.4.6 | up to 6.4.10 | 0C1H1M1L |
| 6.4.5 | up to 6.4.6 | 1C1H1M1L |
| 6.4.4 | up to 6.4.5 | 1C1H2M1L |
| 6.4.0 | up to 6.4.4 | 1C1H2M1L |
| after 6.3.15 | up to 6.4.0 | 0C0H0M0L |
| 6.3.9 | up to 6.3.15 (included) | 0C0H0M1L |
| 6.3.8 | up to 6.3.9 | 0C0H1M1L |
| 6.3.5 | up to 6.3.8 | 0C0H0M1L |
| 6.3.2 | up to 6.3.5 | 0C0H1M1L |
| 6.3.0 | up to 6.3.2 | 0C1H1M1L |
| 6.2.8 | up to 6.3.0 | 0C0H0M0L |
| 6.2.3 | up to 6.2.8 | 0C0H1M0L |
| 6.2.2 | up to 6.2.3 | 0C1H1M0L |
| 6.2.0 | up to 6.2.2 | 0C2H1M0L |
| 6.1.12 | up to 6.2.0 | 0C0H0M0L |
| 6.1.8 | up to 6.1.12 | 0C0H1M0L |
| 6.1.7 | up to 6.1.8 | 0C1H1M0L |
| 6.1.0 | up to 6.1.7 | 0C2H1M0L |
| 6.0.14 | up to 6.1.0 | 0C1H0M0L |
| 6.0.3 | up to 6.0.14 | 0C1H1M0L |
| 6.0.0 | up to 6.0.3 | 0C1H2M0L |
| after 5.8.24 | up to 6.0.0 | 0C0H0M0L |
| 5.8.16 | up to 5.8.24 (included) | 0C0H0M1L |
| 5.8.11 | up to 5.8.16 | 0C0H1M1L |
| 5.8.3 | up to 5.8.11 | 0C1H1M1L |
| 5.8.0 | up to 5.8.3 | 0C1H2M1L |
| after 5.7.22 | up to 5.8.0 | 0C0H0M0L |
| 5.7.14 | up to 5.7.22 (included) | 0C0H0M1L |
| 5.7.12 | up to 5.7.14 | 0C0H1M1L |
| 5.7.8 | up to 5.7.12 | 0C1H1M1L |
| 5.7.5 | up to 5.7.8 | 0C1H2M1L |
| 5.7.0 | up to 5.7.5 | 1C1H2M1L |
| 5.6.9 | up to 5.7.0 | 0C1H1M0L |
| 5.6.4 | up to 5.6.9 | 1C1H1M0L |
| 5.6.0 | up to 5.6.4 | 2C1H2M0L |
| 5.5.7 | up to 5.6.0 | 0C1H1M0L |
| 5.5.1 | up to 5.5.7 | 1C1H2M0L |
| 5.5.0 | up to 5.5.1 | 1C2H2M0L |
| 5.4.11 | up to 5.5.0 | 0C1H2M0L |
| 5.4.7 | up to 5.4.11 | 1C1H2M0L |
| 5.4.0 | up to 5.4.7 | 1C2H2M0L |
| 5.3.10 | up to 5.4.0 | 1C1H2M0L |
| 5.3.2 | up to 5.3.10 | 1C2H2M0L |
| 5.3.0 | up to 5.3.2 | 1C3H3M0L |
| 5.2.11 | up to 5.3.0 | 1C1H2M0L |
| 5.2.4 | up to 5.2.11 | 1C2H2M0L |
| 5.2.0 | up to 5.2.4 | 1C3H3M0L |
| 5.1.10 | up to 5.2.0 | 1C1H1M0L |
| 5.1.5 | up to 5.1.10 | 1C1H2M0L |
| 5.1.2 | up to 5.1.5 | 1C1H3M0L |
| 5.1.0 | up to 5.1.2 | 1C2H3M0L |
| 5.0.16 | up to 5.1.0 | 1C1H1M0L |
| 5.0.12 | up to 5.0.16 | 1C1H2M0L |
| 5.0.1 | up to 5.0.12 | 1C1H3M0L |
| 5.0.0 | up to 5.0.1 | 1C1H4M0L |
| 5.0.0.M2 | up to 5.0.0 | 1C1H1M0L |
| 5.0.0.M1 | up to 5.0.0.M2 | 1C2H1M0L |
| 4.2.16 | up to 5.0.0.M1 | 1C1H1M0L |
| 4.2.13 | up to 4.2.16 | 1C1H2M0L |
| 4.2.12 | up to 4.2.13 | 1C2H2M0L |
| 4.2.4 | up to 4.2.12 | 1C2H3M0L |
| 4.2.3.RELEASE | up to 4.2.4 | 1C2H4M0L |
| 4.2.1.RELEASE | up to 4.2.3.RELEASE | 1C3H4M0L |
| 4.2.0.RELEASE | up to 4.2.1.RELEASE | 1C4H4M0L |
| 4.1.5 | up to 4.2.0.RELEASE | 1C2H2M0L |
| 4.1.4.RELEASE | up to 4.1.5 | 1C2H3M0L |
| 4.1.1 | up to 4.1.4.RELEASE | 1C3H3M0L |
| 4.1.0 | up to 4.1.1 | 1C4H3M0L |
| 4.0.0.RELEASE | up to 4.1.0 | 1C4H2M0L |
| 3.2.10.RELEASE | up to 4.0.0.RELEASE | 1C3H2M0L |
| 3.2.5 | up to 3.2.10.RELEASE | 1C4H2M0L |
| 3.2.2.RELEASE | up to 3.2.5 | 2C4H2M0L |
| 3.2.0 | up to 3.2.2.RELEASE | 2C5H2M0L |
| 3.1.7 | up to 3.2.0 | 1C4H2M0L |
| 3.1.5.RELEASE | up to 3.1.7 | 2C4H2M0L |
| 3.1.3 | up to 3.1.5.RELEASE | 2C5H2M0L |
| 3.1.0 | up to 3.1.3 | 2C5H3M0L |
| 3.0.8 | up to 3.1.0 | 2C4H2M0L |
| 3.0.6 | up to 3.0.8 | 2C4H3M0L |
| 3.0.4 | up to 3.0.6 | 2C4H6M0L |
| 3.0.0 | up to 3.0.4 | 2C4H7M0L |
| 2.0.8 | up to 3.0.0 | 2C4H2M0L |
| 2.0.7 | up to 2.0.8 | 2C4H3M0L |
| 2.0.6 | up to 2.0.7 | 2C4H6M0L |
| 2.0.0 | up to 2.0.6 | 2C4H7M0L |
| before 2.0.0 | all earlier versions | 2C4H5M0L |
No known vulnerabilities in 7.0.5 and later versions
Nothing in our data affects this version.
95 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 31
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2026-22746Spring Security: Spring Security: Timing attack defense bypass allows information disclosure | LOW | 22 Apr 2026 | >=5.7.0, <=5.7.22>=5.8.0, <=5.8.24>=6.3.0, <=6.3.15>=6.4.0, <=6.4.15>=6.5.0, <6.5.10>=7.0.0, <7.0.5 | 6.5.107.0.5 |
| CVE-2026-22751Spring Security: JdbcOneTimeTokenService: Spring Security: Authentication bypass due to race condition in One-Time Token login | MEDIUM | 21 Apr 2026 | >=6.5.0, <6.5.10>=7.0.3, <7.0.5>=6.4.0, <=6.4.13 | 6.5.107.0.5 |
| CVE-2025-22234org.springframework.security/spring-security-core: Spring Security - BCrypt Password Encoder maximum password length breaks timing attack mitigation | MEDIUM | 22 Jan 2026 | >=6.3.8, <6.3.9>=6.4.4, <6.4.5 | 6.3.96.4.5 |
| CVE-2025-41248org.springframework.security/spring-security-core: Spring Security authorization bypass | HIGH | 16 Sep 2025 | >=6.4.0, <6.4.10>=6.5.0, <6.5.4 | 6.4.106.5.4 |
| CVE-2025-41232Spring-Security: Spring Security authorization bypass for method security annotations on private methods | CRITICAL | 21 May 2025 | >=6.4.0, <6.4.6 | 6.4.6 |
| CVE-2025-22223spring-security: authorization bypass via incorrectly locating method security annotations on parameterized types or methods | MEDIUM | 24 Mar 2025 | >=6.4.0, <6.4.4 | 6.4.4 |
| CVE-2024-38827spring-security: authorization bypass for case sensitive comparisons | MEDIUM | 2 Dec 2024 | <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 | 5.7.145.8.166.0.146.1.126.2.86.3.5 |
| CVE-2024-38810spring-security: Missing Authorization When Using @AuthorizeReturnObject | HIGH | 20 Aug 2024 | >=6.3.0, <6.3.2 | 6.3.2 |
| CVE-2024-22257spring-security: Broken Access Control With Direct Use of AuthenticatedVoter | HIGH | 18 Mar 2024 | <5.7.12>=5.8.0, <5.8.11>=6.0.0, <6.1.8>=6.2.0, <6.2.3 | 5.7.125.8.116.1.86.2.3 |
| CVE-2024-22234spring-security: Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated | HIGH | 20 Feb 2024 | >=6.1.0, <6.1.7>=6.2.0, <6.2.2 | 6.1.76.2.2 |
| CVE-2023-20862spring-security: Empty SecurityContext Is Not Properly Saved Upon Logout | MEDIUM | 19 Apr 2023 | >=5.7.0, <5.7.8>=5.8.0, <5.8.3>=6.0.0, <6.0.3 | 5.7.85.8.36.0.3 |
| CVE-2022-31692spring-security: Authorization rules can be bypassed via forward or include dispatcher types in Spring Security | CRITICAL | 31 Oct 2022 | >=5.7.0, <5.7.5>=5.6.0, <5.6.9 | 5.7.55.6.9 |
| CVE-2022-22978springframework: Authorization Bypass in RegexRequestMatcher | CRITICAL | 19 May 2022 | >=5.5.0, <5.5.7>=5.6.0, <5.6.4<5.4.11 | 5.5.75.6.45.4.11 |
| CVE-2022-22976springframework: BCrypt skips salt rounds for work factor of 31 | MEDIUM | 19 May 2022 | >=5.2.0.RELEASE, <5.5.7>=5.6.0, <5.6.4 | 5.5.75.6.4 |
| CVE-2021-22119spring-security: Denial-of-Service (DoS) attack via initiation of Authorization Request | HIGH | 29 Jun 2021 | >=5.5.0, <5.5.1>=5.4.0, <5.4.7>=5.3.0, <5.3.10>=5.2.0, <5.2.11 | 5.5.15.4.75.3.105.2.11 |
| CVE-2020-5408Insufficient Entropy in Spring Security | MEDIUM | 14 May 2020 | >=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 | 5.3.25.2.45.1.105.0.164.2.16 |
| CVE-2020-5407Signature wrapping vulnerability in Spring Security | HIGH | 13 May 2020 | >=5.2.0, <5.2.4>=5.3.0, <5.3.2 | 5.2.45.3.2 |
| CVE-2019-11272spring-security-core: mishandling of user passwords allows logging in with a password of NULL | HIGH | 26 Jun 2019 | <4.2.13 | 4.2.13 |
| CVE-2019-3795spring-security-core: Insecure randomness when using a secureRandom instance constructed by Spring Security | MEDIUM | 9 Apr 2019 | >=4.2.0, <4.2.12>=5.0.0, <5.0.12>=5.1.0, <5.1.5 | 4.2.125.0.125.1.5 |
| CVE-2018-15801Spring Security versions 5.1.x prior to 5.1.2 contain an authorization ... | HIGH | 19 Dec 2018 | >=5.1.0, <5.1.2 | 5.1.2 |
| CVE-2018-1199spring-framework: Improper URL path validation allows for bypassing of security checks on static resources | MEDIUM | 16 Mar 2018 | >=4.2.0, <4.2.4>=5.0.0, <5.0.1>=4.1.0, <4.1.5 | 4.2.45.0.14.1.5 |
| CVE-2017-4995Security: Deserialization of untrusted data via Jackson | HIGH | 27 Nov 2017 | >=4.2.0.RELEASE, <4.2.3.RELEASE>=5.0.0.M1, <5.0.0.M2 | 4.2.3.RELEASE5.0.0.M2 |
| CVE-2016-5007spring: Path matching inconsistency | HIGH | 25 May 2017 | <4.1.1 | 4.1.1 |
| CVE-2014-3527CAS: Access control bypass via untrusted infomation usage in proxy ticket authentication | CRITICAL | 25 May 2017 | <3.1.7>=3.2.0, <3.2.5 | 3.1.73.2.5 |
| CVE-2014-0097Framework: empty passwords may bypass authentication | HIGH | 25 May 2017 | >=3.2.0, <3.2.2.RELEASE>=3.1.0, <3.1.5.RELEASE | 3.2.2.RELEASE3.1.5.RELEASE |
| CVE-2016-9879Security: Improper handling of path parameters allows bypassing the security constraint | HIGH | 6 Jan 2017 | <3.2.10.RELEASE>=4.0.0.RELEASE, <4.1.4.RELEASE>=4.2.0.RELEASE, <4.2.1.RELEASE | 3.2.10.RELEASE4.1.4.RELEASE4.2.1.RELEASE |
| CVE-2012-5055Security: Ability to determine if username is valid via DaoAuthenticationProvider | MEDIUM | 5 Dec 2012 | <2.0.8>=3.0.0, <3.0.8>=3.1.0, <3.1.3 | 2.0.83.0.83.1.3 |
| CVE-2011-2732Security: Header injection flaw due improper use of 'spring-security-redirect' parameter | MEDIUM | 5 Dec 2012 | <2.0.7>=3.0.0, <3.0.6 | 2.0.73.0.6 |
| CVE-2011-2731Security: Privilege escalation by using RunAsManager mechanism | MEDIUM | 5 Dec 2012 | <2.0.7>=3.0.0, <3.0.6 | 2.0.73.0.6 |
| CVE-2011-2894Security: Chosen commands execution on the server (Framework) or authentication token bypass (Security) by objects de-serialization | MEDIUM | 4 Oct 2011 | >=3.0.0, <3.0.6>=2.0.0, <2.0.7 | 3.0.62.0.7 |
| CVE-2010-3700Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security | MEDIUM | 29 Oct 2010 | >=2.0.0, <2.0.6>=3.0.0, <3.0.4 | 2.0.63.0.4 |
Seal Security (Maven)
Seal Security ships a patched build of this package. Its fixed versions:
- CVE-2024-38827: 6.1.3+sp2
- CVE-2026-22746: 5.3.9.RELEASE+sp2
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.