Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider (CVE-2026-22746) | HOL Guard CVE

Low · CVSS 3.7CVE-2026-22746GHSA-VXF7-QJ7Q-83FH

Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider

Answer in brief

CVE-2026-22746 records a Low severity (CVSS 3.7) vulnerability in Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider. The current sources do not mark it as known exploited. The current feed maps org.springframework.security:spring-security-core (maven), org.springframework.security:spring-security-core (maven), org.springframework.security:spring-security-core (maven), org.springframework.security:spring-security-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 22, 2026Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 3.7
Exploitation: Not marked as known exploited
Affected software: 6 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps org.springframework.security:spring-security-core (maven), org.springframework.security:spring-security-core (maven), org.springframework.security:spring-security-core (maven), org.springframework.security:spring-security-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
org.springframework.security:spring-security-coremaven	>=5.7.0	Not reported
org.springframework.security:spring-security-coremaven	>=5.8.0	Not reported
org.springframework.security:spring-security-coremaven	>=6.3.0	Not reported
org.springframework.security:spring-security-coremaven	>=6.4.0	Not reported
org.springframework.security:spring-security-coremaven	>=6.5.0 <6.5.10	6.5.10
org.springframework.security:spring-security-coremaven	>=7.0.0 <7.0.5	7.0.5

Recommended response

Check inventory. Check lockfiles and deployed manifests for org.springframework.security:spring-security-core, org.springframework.security:spring-security-core, org.springframework.security:spring-security-core.
Review the reported fix. Update org.springframework.security:spring-security-core to 6.5.10; org.springframework.security:spring-security-core to 7.0.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Apr 22, 2026
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.