{"answers":{"affected":"4 open source packages ship an affected version, including org.springframework.security:spring-security-aspects and org.springframework.security:spring-security-core.","exploited":"There is no known exploitation of CVE-2025-41232 in the wild and no public exploit code.","fix":"Upgrade org.springframework.security:spring-security-aspects to 6.4.6 or later.","what":"CVE-2025-41232 is a critical missing authorization vulnerability in Spring Security, published on 21 May 2025. 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-41232 and fix it if it is affected.\n\nWhat it is: CVE-2025-41232 is a critical missing authorization vulnerability in Spring Security, published on 21 May 2025. 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-41232 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.security:spring-security-aspects (Maven): affected from 6.4.0; fixed in 6.4.6\n- org.springframework.security:spring-security-aspects (Maven): affected from 6.4.0; fixed in 6.4.6\n- org.springframework.security:spring-security-core (Maven): affected from 6.4.0; fixed in 6.4.6\n- org.springframework.security:spring-security-core (Maven): affected from 6.4.0; fixed in 6.4.6\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-41232/ (Markdown: https://insights.sbomify.com/CVE-2025-41232/index.md)","id":"CVE-2025-41232","markdown":"https://insights.sbomify.com/CVE-2025-41232/index.md","name":"CVE-2025-41232","record":{"aliases":["CLEANSTART-2026-RU90125","GHSA-9pp5-9c7g-4r83","MINI-7mgg-83cr-mcg5","MINI-ffh9-cvqg-2hcw","MINI-hrf6-vg44-7p3j","ROOT-APP-MAVEN-CVE-2025-41232"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Security library","requires_auth":"none","summary":"Attackers can bypass authorization checks on private methods when using AspectJ mode, potentially accessing restricted functionality.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"Spring Security Aspects may not correctly locate method security annotations on private methods. This can cause an authorization bypass.\n\nYour application may be affected by this if the following are true:\n\n  *  You are using @EnableMethodSecurity(mode=ASPECTJ) and spring-security-aspects, and\n  *  You have Spring Security method annotations on a private method\nIn that case, the target method may be able to be invoked without proper authorization.\n\nYou are not affected if:\n\n  *  You are not using @EnableMethodSecurity(mode=ASPECTJ) or spring-security-aspects, or\n  *  You have no Spring Security-annotated private methods","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":"CVE-2025-41232: Spring Security authorization bypass for method security annotations on private methods","id":"CVE-2025-41232","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":4,"n_references":1,"next":{"headline":"SQL injection in Avi Load Balancer","id":"CVE-2025-41233"},"packages":[{"ecosystem":"Maven","fixed":["6.4.6"],"introduced":["6.4.0"],"last_affected":[],"package":"org.springframework.security:spring-security-aspects","purl":null,"source":"GHSA-9pp5-9c7g-4r83"},{"ecosystem":"Maven","fixed":["6.4.6"],"introduced":["6.4.0"],"last_affected":[],"package":"org.springframework.security:spring-security-aspects","purl":"pkg:maven/org.springframework.security/spring-security-aspects","source":"GHSA-9pp5-9c7g-4r83"},{"ecosystem":"Maven","fixed":["6.4.6"],"introduced":["6.4.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-9pp5-9c7g-4r83"},{"ecosystem":"Maven","fixed":["6.4.6"],"introduced":["6.4.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-9pp5-9c7g-4r83"}],"prev":{"headline":"VMware Cloud Foundation Missing Authorisation Vulnerability","id":"CVE-2025-41231"},"products":["Spring Security"],"published":"2025-05-21","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":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Spring"]},"summary":"Attackers can bypass authorization checks on private methods when using AspectJ mode, potentially accessing restricted functionality.","url":"https://insights.sbomify.com/CVE-2025-41232/"}