What is CVE-2025-22228?

CVE-2025-22228 is a high-severity improper authentication vulnerability in org.springframework.security:spring-security-crypto (maven), affecting versions >= 6.3.0, < 6.3.8. It is fixed in 6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2025-22228?

CVE-2025-22228 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.springframework.security:spring-security-crypto are affected by CVE-2025-22228?

org.springframework.security:spring-security-crypto (maven) versions >= 6.3.0, < 6.3.8 is affected.

Is there a fix for CVE-2025-22228?

Yes. CVE-2025-22228 is fixed in 6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16. Upgrade to this version or later.

Is CVE-2025-22228 exploitable, and should I be worried?

Whether CVE-2025-22228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-22228 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-22228

Q: How severe is CVE-2025-22228?

CVE-2025-22228 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2025-22228?

Yes. CVE-2025-22228 is fixed in 6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16. Upgrade to this version or later.

Q: Is CVE-2025-22228 exploitable, and should I be worried?

Whether CVE-2025-22228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-22228 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-22228?

Upgrade: org.springframework.security:spring-security-crypto to 6.3.8 or later, org.springframework.security:spring-security-crypto to 6.4.4 or later, org.springframework.security:spring-security-crypto to 6.2.10 or later, org.springframework.security:spring-security-crypto to 6.1.14 or later, org.springframework.security:spring-security-crypto to 6.0.16 or later, org.springframework.security:spring-security-crypto to 5.8.18 or later, org.springframework.security:spring-security-crypto to 5.7.16 or later.

Summary

Spring Security Does Not Enforce Password Length

BCryptPasswordEncoder.matches(CharSequence,String) will incorrectly return true for passwords larger than 72 characters as long as the first 72 characters are the same.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2025-22228 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16); upgrading removes the vulnerable code path.

Affected versions

org.springframework.security:spring-security-crypto (>= 6.3.0, < 6.3.8) org.springframework.security:spring-security-crypto (>= 6.4.0, < 6.4.4) org.springframework.security:spring-security-crypto (>= 6.2.0, <= 6.2.9) org.springframework.security:spring-security-crypto (>= 6.1.0, <= 6.1.13) org.springframework.security:spring-security-crypto (>= 6.0.0, <= 6.0.15) org.springframework.security:spring-security-crypto (>= 5.8.0, <= 5.8.17) org.springframework.security:spring-security-crypto (<= 5.7.15)

Security releases

org.springframework.security:spring-security-crypto → 6.3.8 (maven) org.springframework.security:spring-security-crypto → 6.4.4 (maven) org.springframework.security:spring-security-crypto → 6.2.10 (maven) org.springframework.security:spring-security-crypto → 6.1.14 (maven) org.springframework.security:spring-security-crypto → 6.0.16 (maven) org.springframework.security:spring-security-crypto → 5.8.18 (maven) org.springframework.security:spring-security-crypto → 5.7.16 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.springframework.security:spring-security-crypto to 6.3.8 or later; org.springframework.security:spring-security-crypto to 6.4.4 or later; org.springframework.security:spring-security-crypto to 6.2.10 or later; org.springframework.security:spring-security-crypto to 6.1.14 or later; org.springframework.security:spring-security-crypto to 6.0.16 or later; org.springframework.security:spring-security-crypto to 5.8.18 or later; org.springframework.security:spring-security-crypto to 5.7.16 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-22228? CVE-2025-22228 is a high-severity improper authentication vulnerability in org.springframework.security:spring-security-crypto (maven), affecting versions >= 6.3.0, < 6.3.8. It is fixed in 6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2025-22228? CVE-2025-22228 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.springframework.security:spring-security-crypto are affected by CVE-2025-22228? org.springframework.security:spring-security-crypto (maven) versions >= 6.3.0, < 6.3.8 is affected.
Is there a fix for CVE-2025-22228? Yes. CVE-2025-22228 is fixed in 6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16. Upgrade to this version or later.
Is CVE-2025-22228 exploitable, and should I be worried? Whether CVE-2025-22228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-22228 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-22228?
- Upgrade org.springframework.security:spring-security-crypto to 6.3.8 or later
- Upgrade org.springframework.security:spring-security-crypto to 6.4.4 or later
- Upgrade org.springframework.security:spring-security-crypto to 6.2.10 or later
- Upgrade org.springframework.security:spring-security-crypto to 6.1.14 or later
- Upgrade org.springframework.security:spring-security-crypto to 6.0.16 or later
- Upgrade org.springframework.security:spring-security-crypto to 5.8.18 or later
- Upgrade org.springframework.security:spring-security-crypto to 5.7.16 or later