# Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide

Advisory record · `GHSA-vqxh-445g-37fc`

- **Identifiers:** `GHSA-vqxh-445g-37fc` · `CVE-2025-22234`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-208](https://cwe.mitre.org/data/definitions/208.html)
- **Tags:** [CWE-208](https://agentprime.io/advisories/tag/cwe-208.md)
- **Published:** 22 Jan 2026
- **Updated:** 3 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Jan 2026, 21:33 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.3.8, <6.3.9 || >=6.4.4, <6.4.5`; fixed in `6.3.9`, `6.4.5`

## 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vqxh-445g-37fc)

## Sources

- [GitHub Advisory Database: GHSA-vqxh-445g-37fc](https://github.com/advisories/GHSA-vqxh-445g-37fc)
- [OSV: GHSA-vqxh-445g-37fc](https://osv.dev/vulnerability/GHSA-vqxh-445g-37fc)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-22234>
- <https://github.com/spring-projects/spring-security>
- <https://spring.io/security/cve-2025-22234>

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-vqxh-445g-37fc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vqxh-445g-37fc/>. Everything for agents: <https://agentprime.io/llms.txt>.