CVE-2025-22234: Spring Security - BCrypt Password Encoder maximum password length breaks timing attack mitigation

Published Jan 22, 2026
·
Updated

The fix applied in CVE-2025-22228 inadvertently broke the timing attack mitigation implemented in DaoAuthenticationProvider. This can allow attackers to infer valid usernames or other authentication behavior via response-time differences under certain configurations.

Affected Software

3 affected componentsFixes available
Spring Spring Security
maven/org.springframework.security:spring-security-core=6.4.4
6.4.5
maven/org.springframework.security:spring-security-core=6.3.8
6.3.9

Remediation

Information

Upgrade to a fixed version: 5.7.17, 5.8.19, 6.0.17, 6.1.15, 6.2.11, 6.3.9, or 6.4.5 (depending on your release line).

Event History

Jan 22, 2026
CVE Published
via MITRE·09:02 PM
Data Sourced
via MITRE·09:02 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:33 PM
Data Sourced
via GitHub·09:33 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-22234?

CVE-2025-22234 is categorized as a high severity vulnerability due to its potential to allow timing attacks that can expose valid usernames.

2

How do I fix CVE-2025-22234?

To address CVE-2025-22234, upgrade to Spring Security version 6.4.5 or 6.3.9.

3

What are the risks associated with not fixing CVE-2025-22234?

Failure to fix CVE-2025-22234 may lead to unauthorized access through username enumeration via timing attacks.

4

Which versions of Spring Security are affected by CVE-2025-22234?

CVE-2025-22234 affects Spring Security versions 6.4.4 and 6.3.8.

5

Is CVE-2025-22234 related to any previous vulnerabilities?

CVE-2025-22234 is related to CVE-2025-22228 as the fix implemented for it inadvertently introduced this vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203