Skip to content

GHSA-9pp5-9c7g-4r83 CVE-2025-41232

Spring Security authorization bypass for method security annotations on private methods

Critical Maven
Severity
9.1 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
0.62%
Chance of exploitation in the next 30 days. Higher than 49.82% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-693 Protection Mechanism Failure
Fix
Available
2 packages have a fixed version

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

Affected versions

Maven

PackageVulnerableFixed in
org.springframework.security:spring-security-aspects
>= 6.4.0, < 6.4.6
6.4.6
org.springframework.security:spring-security-core
>= 6.4.0, < 6.4.6
6.4.6

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.springframework.security:spring-security-aspects Maven → 6.4.6

maven
<dependency><groupId>org.springframework.security</groupId><artifactId>spring-security-aspects</artifactId><version>6.4.6</version></dependency>
gradle
implementation("org.springframework.security:spring-security-aspects:6.4.6")

org.springframework.security:spring-security-core Maven → 6.4.6

maven
<dependency><groupId>org.springframework.security</groupId><artifactId>spring-security-core</artifactId><version>6.4.6</version></dependency>
gradle
implementation("org.springframework.security:spring-security-core:6.4.6")

Severity breakdown

CVSS 3.1 9.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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

Weakness

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vxf7-qj7q-83fh
Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider
Low Also affects org.springframework.security:spring-security-core
GHSA-x2wq-9x2f-fhj7
Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured
Medium Also affects org.springframework.security:spring-security-core
GHSA-vqxh-445g-37fc
Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide
Medium Also affects org.springframework.security:spring-security-core
GHSA-8v5q-rhf3-jphm
Spring Security annotation detection mechanism has authorization bypass
High Also affects org.springframework.security:spring-security-core
GHSA-hh3m-g4qj-4835
Spring Security Vulnerable to Authorization Bypass via Security Annotations
Medium Also affects org.springframework.security:spring-security-core
GHSA-q3v6-hm2v-pw99
Spring Framework has Authorization Bypass for Case Sensitive Comparisons
Medium Also affects org.springframework.security:spring-security-core
GHSA-hmqf-wpq9-jq83
Spring Security Missing Authorization vulnerability
High Also affects org.springframework.security:spring-security-core
GHSA-f3jh-qvm4-mg39
Erroneous authentication pass in Spring Security
High Also affects org.springframework.security:spring-security-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor