Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated
Published 20 Feb 2024 · Updated 13 Feb 2025
Is your project on an affected org.springframework.security:spring-security-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=6.1.0 <6.1.7
- Fixed in
- 6.1.7
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.1.7 -DforceVersion=true- Affected
- >=6.2.0 <6.2.2
- Fixed in
- 6.2.2
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.2.2 -DforceVersion=trueDetails
In Spring Security, versions 6.1.x prior to 6.1.7 and versions 6.2.x prior to 6.2.2, an application is vulnerable to broken access control when it directly uses the AuthenticationTrustResolver.isFullyAuthenticated(Authentication) method.
Specifically, an application is vulnerable if:
- The application uses AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly and a null authentication parameter is passed to it resulting in an erroneous true return value.
An application is not vulnerable if any of the following is true:
- The application does not use AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly.
- The application does not pass null to AuthenticationTrustResolver.isFullyAuthenticated
- The application only uses isFullyAuthenticated via Method Security https://docs.spring.io/spring-security/reference/servlet/authorization/method-security.html or HTTP Request Security https://docs.spring.io/spring-security/reference/servlet/authorization/authorize-http-requests.html
Is GHSA-w3w6-26f2-p474 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-core, and gives you the command that fixes it.
More advisories for org.springframework.security:spring-security-core
- LowCVE-2026-22746Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider · 22 Apr 2026
- MediumCVE-2026-22751Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured · 21 Apr 2026
- MediumCVE-2025-22234Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide · 22 Jan 2026
- HighCVE-2025-41248Spring Security annotation detection mechanism has authorization bypass · 16 Sept 2025
- CriticalCVE-2025-41232Spring Security authorization bypass for method security annotations on private methods · 21 May 2025
- MediumCVE-2025-22223Spring Security Vulnerable to Authorization Bypass via Security Annotations · 24 Mar 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.