How severe is GHSA-x2wq-9x2f-fhj7?

GHSA-x2wq-9x2f-fhj7 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-x2wq-9x2f-fhj7?

GHSA-x2wq-9x2f-fhj7 affects the following packages: org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-x2wq-9x2f-fhj7?

Update org.springframework.security:spring-security-core to 6.5.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2wq-9x2f-fhj7 is resolved across your whole dependency graph.

How do I detect GHSA-x2wq-9x2f-fhj7 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-x2wq-9x2f-fhj7 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-x2wq-9x2f-fhj7?

O3 pinpoints whether GHSA-x2wq-9x2f-fhj7 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-x2wq-9x2f-fhj7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x2wq-9x2f-fhj7 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.

When was GHSA-x2wq-9x2f-fhj7 published, and has it been updated?

GHSA-x2wq-9x2f-fhj7 was published on April 21, 2026 and was last updated on July 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-x2wq-9x2f-fhj7

MEDIUM

GHSA-x2wq-9x2f-fhj7 is a medium-severity (CVSS 4.8) vulnerability in org.springframework.security:spring-security-core. O3 Security confirms whether GHSA-x2wq-9x2f-fhj7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured

Also known asCVE-2026-22751

Published

Apr 21, 2026

Updated

Jul 17, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

☕org.springframework.security:spring-security-core☕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

Vulnerability in Spring Spring Security. Applications that explicitly configure One-Time Token login with JdbcOneTimeTokenService are vulnerable to a Time-of-check Time-of-use (TOCTOU) race condition. This issue affects Spring Security: from 6.4.0 through 6.4.15, from 6.5.0 through 6.5.9, from 7.0.0 through 7.0.4.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.security:spring-security-core`	≥ 6.5.0&&< 6.5.10	6.5.10
☕Maven	`org.springframework.security:spring-security-core`	≥ 7.0.3&&< 7.0.5	7.0.5
☕Maven	`org.springframework.security:spring-security-core`	≥ 6.4.0	No fix

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.5.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2wq-9x2f-fhj7 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-x2wq-9x2f-fhj7 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-x2wq-9x2f-fhj7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-x2wq-9x2f-fhj7 in your dependencies?

O3 detects GHSA-x2wq-9x2f-fhj7 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