VDB

CVE-2025-22234

CVE-2025-22234 PUBLISHED CVSS 5.3 MEDIUM

Reported by vmware · Published January 22, 2026

spring-security-core is fixed in 6.4.5, 6.4.4, 6.3.9 and 1 more (Maven Central)

The fix applied in CVE-2025-22228 inadvertently broke the timing attack mitigation implemented in DaoAuthenticationProvider. This can allow attackers to infer valid usernames or other authentication behavior via response-time differences under certain configurations.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
org.springframework.security:spring-security-coreMaven Central6.4.5, 6.4.4, 6.3.9, 6.3.8

Risk scores

CVSS 3.1
5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

VendorProductVersions
SpringSpring Security5.7.16, 5.8.18, 6.0.16
SpringSpring Security5.7.16, 5.8.18, 6.0.16
Mavenorg.springframework.security:spring-security-core6.3.8, 6.3.8, 6.4.4

Timeline

  • Apr 22, 2025 CVE Published
  • Apr 23, 2025 PoC Published (13 in total, the first dated here)
  • Jan 22, 2026 CVE Updated
  • Jan 23, 2026 EPSS Score (30 in total, the first dated here)
  • Mar 17, 2026 Security Advisory
  • Jun 19, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-22234
vulnetix vdb fixes CVE-2025-22234

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-22234/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›