pring 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
| Link | Resource |
|---|---|
| http://spring.io/security/cve-2025-41232 |
No configuration.
21 May 2025, 20:24
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Published : 2025-05-21 12:16
Updated : 2025-05-21 20:24
NVD link : CVE-2025-41232
Mitre link : CVE-2025-41232
CVE.ORG link : CVE-2025-41232
JSON object : View
No product.
Protection Mechanism Failure