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

Advisory record · `GHSA-x2wq-9x2f-fhj7`

- **Identifiers:** `GHSA-x2wq-9x2f-fhj7` · `CVE-2026-22751`
- **State:** Confirmed
- **Severity:** CVSS 4.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-367](https://cwe.mitre.org/data/definitions/367.html)
- **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md)
- **Published:** 21 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Apr 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.springframework.security:spring-security-core` (Maven): affected `>=6.5.0, <6.5.10 || >=7.0.3, <7.0.5 || >=6.4.0, <=6.4.13`; fixed in `6.5.10`, `7.0.5`

## Machine-written summary

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

> Spring Security Core versions 6.4.0 through 6.4.13, 6.5.0 through 6.5.9, and 7.0.0 through 7.0.4 are affected when One-Time Token login is configured with JdbcOneTimeTokenService. A time-of-check time-of-use race condition exists in this setup, but the source gives few details on how an attacker would trigger it or what they could gain. Upgrade spring-security-core to 6.5.10 or 7.0.5.

Written 2 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

- 4.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (vmware)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 2nd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x2wq-9x2f-fhj7)

## Sources

- [GitHub Advisory Database: GHSA-x2wq-9x2f-fhj7](https://github.com/advisories/GHSA-x2wq-9x2f-fhj7)
- [OSV: GHSA-x2wq-9x2f-fhj7](https://osv.dev/vulnerability/GHSA-x2wq-9x2f-fhj7)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-22751>
- <https://github.com/spring-projects/spring-security/commit/163772775036c4146815a5266874278c6f45f047>
- <https://github.com/spring-projects/spring-security/commit/4187af38b251fc97fdf9949f7869618111e6e261>
- <https://github.com/spring-projects/spring-security>
- <https://jinyeong.seol.pro/blogs/cve-2026-22751/en>
- <https://spring.io/security/cve-2026-22751>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x2wq-9x2f-fhj7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x2wq-9x2f-fhj7/>. Everything for agents: <https://agentprime.io/llms.txt>.