Skip to content

Spring Security authorization bypass for method security annotations on private methods

Critical severity GitHub Reviewed Published May 21, 2025 to the GitHub Advisory Database • Updated May 21, 2025

Package

maven org.springframework.security:spring-security-aspects (Maven)

Affected versions

>= 6.4.0, < 6.4.6

Patched versions

6.4.6

Description

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

References

Published by the National Vulnerability Database May 21, 2025
Published to the GitHub Advisory Database May 21, 2025
Last updated May 21, 2025
Reviewed May 21, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

CVE ID

CVE-2025-41232

GHSA ID

GHSA-9pp5-9c7g-4r83

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.