CVE-2025-41232: Spring Security authorization bypass for method security annotations on private methods
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.4.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Spring Security Aspects may not correctly locate method security annotations on private methods. This can cause an authorization bypass. Your application may be affected by this if the following are true: • You are using @EnableMethodSecurity(mode=ASPECTJ) and spring-security-aspects, and • You have Spring Security method annotations on a private method In that case, the target method may be able to be invoked without proper authorization. You are not affected if: • You are not using @EnableMethodSecurity(mode=ASPECTJ) or spring-security-aspects, or • You have no Spring Security-annotated private methods
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Spring Security
From 6.4.x · fixed in 6.4.6
- org.springframework.security:spring-security-aspectsMaven
From 6.4.0 · fixed in 6.4.6
- org.springframework.security:spring-security-coreMaven
From 6.4.0 · fixed in 6.4.6