CVE-2026-22746 — spring-security-core
LOWCVE-2026-22746 is a low-severity (CVSS 3.7) CWE-208 vulnerability in org.springframework.security:spring-security-core. A fix is available for org.springframework.security:spring-security-core — see the affected versions and patch details below.
User Attribute Enumeration when Using DaoAuthenticationProvider
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22746.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Vulnerability in Spring Spring Security. If an application is using the UserDetails#isEnabled, #isAccountNonExpired, or #isAccountNonLocked user attributes, to enable, expire, or lock users, then DaoAuthenticationProvider's timing attack defense can be bypassed for users who are disabled, expired, or locked. This issue affects Spring Security: from 5.7.0 through 5.7.22, from 5.8.0 through 5.8.24, from 6.3.0 through 6.3.15, from 6.5.0 through 6.5.9, from 7.0.0 through 7.0.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-core | ≥ 5.7.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 5.8.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 6.3.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 6.4.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 6.5.0&&< 6.5.10 | 6.5.10org.springframework.security:spring-security-core:6.5.10 |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 7.0.0&&< 7.0.5 | 7.0.5org.springframework.security:spring-security-core:7.0.5 |
Affected Products
spring securityvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2026-22746; check the affected-versions list above or the advisory for the patched release of org.springframework.security:spring-security-core, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-22746 in your dependencies?
Find it across Maven, including transitive dependencies.