CVE-2026-22746: User Attribute Enumeration when Using DaoAuthenticationProvider
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: spring security 5.7.23; spring security 5.8.25; spring security 6.3.16; spring security 6.4.16; spring security 6.5.10; spring security 7.0.5 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Vulnerability in Spring Spring Security. If an application is using the UserDetails#isEnabled, #isAccountNonExpired, or #isAccountNonLocked user attributes, to enable, expire, or lock users, then DaoAuthenticationProvider's timing attack defense can be bypassed for users who are disabled, expired, or locked.This issue affects Spring Security: from 5.7.0 through 5.7.22, from 5.8.0 through 5.8.24, from 6.3.0 through 6.3.15, from 6.5.0 through 6.5.9, from 7.0.0 through 7.0.4.
- weakness
- Not named by the CNA. NVD maps it to CWE-208.
- affected
- Spring Security
- published ranges
- vmware spring security < 5.7.23; vmware spring security >= 5.8.0 < 5.8.25; vmware spring security >= 6.3.0 < 6.3.16; vmware spring security >= 6.4.0 < 6.4.16; and 2 more on the CVE page
- first unaffected version, by branch
- spring security 5.7.23; spring security 5.8.25; spring security 6.3.16; spring security 6.4.16; spring security 6.5.10; spring security 7.0.5
- fixed by package (from OSV advisories)
- org.springframework.security:spring-security-core (Maven): 6.5.10; 7.0.5 GHSA-vxf7-qj7q-83fh
- severity
- 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- assigned by
- vmware
- published
- 2026-04-22
check us spring.io
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 22 Apr 2026 | 0.00037 | |
| 25 Apr 2026 | 0.00045 | |
| 28 Apr 2026 | 0.00054 | |
| 17 May 2026 | 0.00057 | |
| 24 May 2026 | 0.00067 | |
| 15 Jun 2026 | 0.00215 | scoring model v2026.06.15 |
6 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: spring security 5.7.23; spring security 5.8.25; spring security 6.3.16; spring security 6.4.16; spring security 6.5.10; spring security 7.0.5. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-22746', '2026-10-31T23:59:59.999999Z', now());