# CVE-2025-22228: CVE-2025-22228: Spring Security BCryptPasswordEncoder does not enforce maximum password length > Attackers can bypass authentication by providing passwords that share the first 72 characters with the valid password, exploiting BCrypt's truncation behavior. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2025 - **Updated:** 26 Feb 2026 - **Also known as:** CLEANSTART-2026-QB26194, CLSA-2025-1742947247, ECHO-0d82-8e9f-d92a, GHSA-mg83-c7gq-rv5c, MINI-5jfg-gm2f-5p33, MINI-6x3f-vp3m-79mf, MINI-m98r-gg6p-r796, MINI-wpmv-6xv7-c8fv, RHLW-2026-351d5430e078d751, ROOT-APP-MAVEN-CVE-2025-22228 ## What is CVE-2025-22228? CVE-2025-22228 is a high-severity authentication bypass vulnerability in Spring Security, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description BCryptPasswordEncoder.matches(CharSequence,String) will incorrectly return true for passwords larger than 72 characters as long as the first 72 characters are the same. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2025-22228? 14 open source packages ship an affected version, including org.springframework.security:spring-security-crypto. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.security:spring-security-crypto` | Maven | All versions | 5.7.16 | | `org.springframework.security:spring-security-crypto` | Maven | All versions | 5.7.16 | | `org.springframework.security:spring-security-crypto` | Maven | From 5.8.0 | 5.8.18 | | `org.springframework.security:spring-security-crypto` | Maven | From 5.8.0 | 5.8.18 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.0.0 | 6.0.16 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.0.0 | 6.0.16 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.1.0 | 6.1.14 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.1.0 | 6.1.14 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.2.0 | 6.2.10 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.2.0 | 6.2.10 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.3.0 | 6.3.8 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.3.0 | 6.3.8 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.4.0 | 6.4.4 | | `org.springframework.security:spring-security-crypto` | Maven | From 6.4.0 | 6.4.4 | ## How do I fix CVE-2025-22228? Upgrade org.springframework.security:spring-security-crypto to a fixed version for your release line: 5.7.16, 5.8.18, 6.0.16 or 6.1.14. ## Is CVE-2025-22228 being exploited? There is no known exploitation of CVE-2025-22228 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22228 and fix it if it is affected. What it is: CVE-2025-22228 is a high-severity authentication bypass vulnerability in Spring Security, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-22228 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.security:spring-security-crypto (Maven): affected all versions; fixed in 5.7.16 - org.springframework.security:spring-security-crypto (Maven): affected all versions; fixed in 5.7.16 - org.springframework.security:spring-security-crypto (Maven): affected from 5.8.0; fixed in 5.8.18 - org.springframework.security:spring-security-crypto (Maven): affected from 5.8.0; fixed in 5.8.18 - org.springframework.security:spring-security-crypto (Maven): affected from 6.0.0; fixed in 6.0.16 - org.springframework.security:spring-security-crypto (Maven): affected from 6.0.0; fixed in 6.0.16 - org.springframework.security:spring-security-crypto (Maven): affected from 6.1.0; fixed in 6.1.14 - org.springframework.security:spring-security-crypto (Maven): affected from 6.1.0; fixed in 6.1.14 - org.springframework.security:spring-security-crypto (Maven): affected from 6.2.0; fixed in 6.2.10 - org.springframework.security:spring-security-crypto (Maven): affected from 6.2.0; fixed in 6.2.10 - org.springframework.security:spring-security-crypto (Maven): affected from 6.3.0; fixed in 6.3.8 - org.springframework.security:spring-security-crypto (Maven): affected from 6.3.0; fixed in 6.3.8 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-22228/ (Markdown: https://insights.sbomify.com/CVE-2025-22228/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22228 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22228 - OSV: https://osv.dev/vulnerability/CVE-2025-22228 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22228/ Summaries are generated and may contain mistakes; the official description above is the record.