Spring Security uses insufficiently random values
Spring Security versions 4.2.x prior to 4.2.12, 5.0.x prior to 5.0.12, and 5.1.x prior to 5.1.5 contain an insecure randomness vulnerability when using SecureRandomFactoryBean#setSeed to configure a SecureRandom instance. In order to be impacted, an honest application must provide a seed and make the resulting random material available to an attacker for inspection.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.springframework.security:spring-security-core | >= 4.2.0, < 4.2.12, >= 5.0.0, < 5.0.12, >= 5.1.0, < 5.1.5 | 4.2.12, 5.0.12, 5.1.5 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Weakness (CWE)
CWE-330- Platform
- Java / Kotlin (Maven)
- Package
org.springframework.security:spring-security-core- Disclosed
- 16.04.2019
- Updated
- 11.10.2026 11:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-v2r2-7qm7-jj6v - CC BY 4.0
Vulnerability history: org.springframework.security:spring-security-core
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 31
- First → latest
- 10.2018 04.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 4
- High 11
- Medium 15
- Low 1
Disclosures per year
- 2018: 3
- 2019: 2
- 2020: 4
- 2021: 1
- 2022: 10
- 2023: 1
- 2024: 4
- 2025: 3
- 2026: 3
-
Spring Security uses insufficiently random values this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.