CVE-2026-22746: Vulnerability in Spring Spring Security
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.
AI Analysis
Technical Summary
This vulnerability in Spring Security arises when applications rely on UserDetails attributes (isEnabled, isAccountNonExpired, isAccountNonLocked) to control user access states. Under these conditions, the timing attack defense implemented in DaoAuthenticationProvider can be bypassed for users who are disabled, expired, or locked. This bypass could allow an attacker to infer user account states through timing analysis. The affected versions span multiple major releases from 5.7.0 to 7.0.4. The CVSS v3.1 base score is 3.7, indicating a low severity with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, and limited confidentiality impact.
Potential Impact
The impact is limited to potential information disclosure about user account states via timing attack bypass. There is no indication of privilege escalation, data modification, or denial of service. The confidentiality impact is low, and no integrity or availability impacts are reported. No known exploits are currently in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, applications should review their use of UserDetails attributes for user state management and consider additional mitigations to prevent timing attack information leakage. Monitor official Spring Security advisories for updates and patches addressing this issue.
CVE-2026-22746: Vulnerability in Spring Spring Security
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Spring Security arises when applications rely on UserDetails attributes (isEnabled, isAccountNonExpired, isAccountNonLocked) to control user access states. Under these conditions, the timing attack defense implemented in DaoAuthenticationProvider can be bypassed for users who are disabled, expired, or locked. This bypass could allow an attacker to infer user account states through timing analysis. The affected versions span multiple major releases from 5.7.0 to 7.0.4. The CVSS v3.1 base score is 3.7, indicating a low severity with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, and limited confidentiality impact.
Potential Impact
The impact is limited to potential information disclosure about user account states via timing attack bypass. There is no indication of privilege escalation, data modification, or denial of service. The confidentiality impact is low, and no integrity or availability impacts are reported. No known exploits are currently in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, applications should review their use of UserDetails attributes for user state management and consider additional mitigations to prevent timing attack information leakage. Monitor official Spring Security advisories for updates and patches addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-01-09T06:55:03.990Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e8609e19fe3cd2cd714513
Added to database: 4/22/2026, 5:46:06 AM
Last enriched: 4/22/2026, 6:01:34 AM
Last updated: 4/22/2026, 7:58:02 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.