Advisory record · GHSA-w3w6-26f2-p474

Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

CVSS 7.4 HighEPSS 0.0068 · 53rd percentile

Published by the GitHub Advisory Database at 20 Feb 2024, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.security:spring-security-coreMaven>=6.1.0, <6.1.7 || >=6.2.0, <6.2.26.1.7, 6.2.2
Identifiers
GHSA-w3w6-26f2-p474 · CVE-2024-22234
Weakness (CWE)
CWE-284
Published
20 Feb 2024
Updated
13 Feb 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring Security (spring-security-core) versions 6.1.0 through 6.1.6 and 6.2.0 through 6.2.1 are affected. An application that calls AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly and passes it a null authentication can receive a true result in error, which leads to broken access control. Applications that do not call this method directly, or that use it only through method security or HTTP request security, are not affected. Upgrade to spring-security-core 6.1.7 or 6.2.2.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0068, the 53rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.