How severe is GHSA-w3w6-26f2-p474?

GHSA-w3w6-26f2-p474 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w3w6-26f2-p474?

GHSA-w3w6-26f2-p474 affects the following packages: org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w3w6-26f2-p474?

Update org.springframework.security:spring-security-core to 6.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3w6-26f2-p474 is resolved across your whole dependency graph.

How do I detect GHSA-w3w6-26f2-p474 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w3w6-26f2-p474 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-w3w6-26f2-p474?

O3 pinpoints whether GHSA-w3w6-26f2-p474 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w3w6-26f2-p474 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w3w6-26f2-p474 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w3w6-26f2-p474?

GHSA-w3w6-26f2-p474 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w3w6-26f2-p474?

GHSA-w3w6-26f2-p474 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w3w6-26f2-p474 published, and has it been updated?

GHSA-w3w6-26f2-p474 was published on February 20, 2024 and was last updated on February 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-w3w6-26f2-p474: spring-security-core (High 7.4)

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk48th percentile-0.97%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.security:spring-security-core`	≥ 6.1.0&&< 6.1.7	6.1.7
☕Maven	`org.springframework.security:spring-security-core`	≥ 6.2.0&&< 6.2.2	6.2.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.security:spring-security-core to 6.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3w6-26f2-p474 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w3w6-26f2-p474 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w3w6-26f2-p474. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 Authenticatio

O3 Security · Impact-Aware SCA

Is GHSA-w3w6-26f2-p474 in your dependencies?

O3 detects GHSA-w3w6-26f2-p474 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-w3w6-26f2-p474