{"answers":{"affected":"4 open source packages ship an affected version, including org.springframework.security:spring-security-core.","exploited":"There is no known exploitation of CVE-2025-22234 in the wild and no public exploit code.","fix":"Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 6.3.9 or 6.4.5.","what":"CVE-2025-22234 is a medium-severity vulnerability in Spring Security, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22234 and fix it if it is affected.\n\nWhat it is: CVE-2025-22234 is a medium-severity vulnerability in Spring Security, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-22234 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.security:spring-security-core (Maven): affected from 6.3.8; fixed in 6.3.9\n- org.springframework.security:spring-security-core (Maven): affected from 6.3.8; fixed in 6.3.9\n- org.springframework.security:spring-security-core (Maven): affected from 6.4.4; fixed in 6.4.5\n- org.springframework.security:spring-security-core (Maven): affected from 6.4.4; fixed in 6.4.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-22234/ (Markdown: https://insights.sbomify.com/CVE-2025-22234/index.md)","id":"CVE-2025-22234","markdown":"https://insights.sbomify.com/CVE-2025-22234/index.md","name":"CVE-2025-22234","record":{"aliases":["CLSA-2025-1754525015","GHSA-vqxh-445g-37fc","MINI-5h5q-p2m5-f2gc","MINI-7mf5-6q3c-8rh6","MINI-8794-24gr-ffq5"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Security library","requires_auth":"none","summary":"Attackers can infer valid usernames via timing differences due to a broken mitigation in Spring Security's BCrypt encoder under specific configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Spring Security - BCrypt Password Encoder maximum password length breaks timing attack mitigation","id":"CVE-2025-22234","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":4,"n_references":1,"next":{"headline":"Spring Boot EndpointRequest.to() creates wrong matcher if actuator endpoint is not exposed","id":"CVE-2025-22235"},"packages":[{"ecosystem":"Maven","fixed":["6.3.9"],"introduced":["6.3.8"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-vqxh-445g-37fc"},{"ecosystem":"Maven","fixed":["6.3.9"],"introduced":["6.3.8"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-vqxh-445g-37fc"},{"ecosystem":"Maven","fixed":["6.4.5"],"introduced":["6.4.4"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-vqxh-445g-37fc"},{"ecosystem":"Maven","fixed":["6.4.5"],"introduced":["6.4.4"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-vqxh-445g-37fc"}],"prev":{"headline":"Spring Framework DataBinder Case Sensitive Match Exception","id":"CVE-2025-22233"},"products":["Spring Security"],"published":"2026-01-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["Spring"]},"summary":"Attackers can infer valid usernames via timing differences due to a broken mitigation in Spring Security's BCrypt encoder under specific configurations.","url":"https://insights.sbomify.com/CVE-2025-22234/"}