CriticalGHSA-9pp5-9c7g-4r83CVE-2025-41232

Spring Security authorization bypass for method security annotations on private methods

Published 21 May 2025 · Updated 16 Oct 2025

Is your project on an affected org.springframework.security:spring-security-aspects?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=6.4.0 <6.4.6
Fixed in
6.4.6
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-aspects -DdepVersion=6.4.6 -DforceVersion=true
Affected
>=6.4.0 <6.4.6
Fixed in
6.4.6
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.4.6 -DforceVersion=true

Details

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

Is GHSA-9pp5-9c7g-4r83 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework.security:spring-security-aspects, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.