Answer in brief
CVE-2024-6832 records a Unknown severity vulnerability in Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon User Manager Kernel (generic), WSO2/WSO2 Enterprise Integrator (generic) 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.
A CVSS score is not reported in the current record. 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.
The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon User Manager Kernel (generic), WSO2/WSO2 Enterprise Integrator (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Control Planegeneric | >=4.5.0 <4.5.0.40 || >=4.6.0 <4.6.0.4 || >=4.6.0 <4.6.0.5 | 4.5.0.40, 4.6.0.4, 4.6.0.5 |
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.296 || >=3.2.0 <3.2.0.386 || >=3.2.0 <3.2.0.455 || >=3.2.1 <3.2.1.74 || >=4.1.0 <4.1.0.238 || >=4.2.0 <4.2.0.179 || >=4.3.0 <4.3.0.91 || >=4.4.0 <4.4.0.55 || >=4.5.0 <4.5.0.39 || >=4.6.0 <4.6.0.4 | 3.1.0.296, 3.2.0.386, 3.2.0.455, 3.2.1.74, 4.1.0.238, 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.39, 4.6.0.4 |
| WSO2/WSO2 Carbon User Manager Kernelgeneric | >=4.5.0 <4.5.0.7 || >=4.5.3 <4.5.3.53 || >=4.6.0 <4.6.0.196 || >=4.6.1 <4.6.1.163 || >=4.6.1 <4.6.1.164 || >=4.6.3 <4.6.3.44 || >=4.6.4 <4.6.4.25 || >=4.7.1 <4.7.1.77 || >=4.7.1 <4.7.1.78 || >=4.8.1 <4.8.1.46 || >=4.9.26 <4.9.26.33 || >=4.9.27 <4.9.27.19 || >=4.9.28 <4.9.28.21 || >=4.9.33 <4.9.33.4 || >=4.10.9 <4.10.9.49 | 4.5.0.7, 4.5.3.53, 4.6.0.196, 4.6.1.163, 4.6.1.164, 4.6.3.44, 4.6.4.25, 4.7.1.77, 4.7.1.78, 4.8.1.46, 4.9.26.33, 4.9.27.19, 4.9.28.21, 4.9.33.4, 4.10.9.49 |
| WSO2/WSO2 Enterprise Integratorgeneric | >=6.6.0 <6.6.0.229 | 6.6.0.229 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.320 || >=5.11.0 <5.11.0.427 || >=6.0.0 <6.0.0.254 || >=6.1.0 <6.1.0.195 || >=7.0.0 <7.0.0.82 | 5.10.0.320, 5.11.0.427, 6.0.0.254, 6.1.0.195, 7.0.0.82 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.314 | 5.10.0.314 |
| WSO2/WSO2 Open Banking AMgeneric | >=2.0.0 <2.0.0.345 | 2.0.0.345 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.366 | 2.0.0.366 |
| WSO2/WSO2 Traffic Managergeneric | >=4.5.0 <4.5.0.38 || >=4.6.0 <4.6.0.4 || >=4.6.0 <4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
| WSO2/WSO2 Universal Gatewaygeneric | >=4.5.0 <4.5.0.38 || >=4.6.0 <4.6.0.4 || >=4.6.0 <4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-6832 records a Unknown severity vulnerability in Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon User Manager Kernel (generic), WSO2/WSO2 Enterprise Integrator (generic) 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.
A CVSS score is not reported in the current record. 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.
The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon User Manager Kernel (generic), WSO2/WSO2 Enterprise Integrator (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Control Planegeneric | >=4.5.0 <4.5.0.40 || >=4.6.0 <4.6.0.4 || >=4.6.0 <4.6.0.5 | 4.5.0.40, 4.6.0.4, 4.6.0.5 |
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.296 || >=3.2.0 <3.2.0.386 || >=3.2.0 <3.2.0.455 || >=3.2.1 <3.2.1.74 || >=4.1.0 <4.1.0.238 || >=4.2.0 <4.2.0.179 || >=4.3.0 <4.3.0.91 || >=4.4.0 <4.4.0.55 || >=4.5.0 <4.5.0.39 || >=4.6.0 <4.6.0.4 | 3.1.0.296, 3.2.0.386, 3.2.0.455, 3.2.1.74, 4.1.0.238, 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.39, 4.6.0.4 |
| WSO2/WSO2 Carbon User Manager Kernelgeneric | >=4.5.0 <4.5.0.7 || >=4.5.3 <4.5.3.53 || >=4.6.0 <4.6.0.196 || >=4.6.1 <4.6.1.163 || >=4.6.1 <4.6.1.164 || >=4.6.3 <4.6.3.44 || >=4.6.4 <4.6.4.25 || >=4.7.1 <4.7.1.77 || >=4.7.1 <4.7.1.78 || >=4.8.1 <4.8.1.46 || >=4.9.26 <4.9.26.33 || >=4.9.27 <4.9.27.19 || >=4.9.28 <4.9.28.21 || >=4.9.33 <4.9.33.4 || >=4.10.9 <4.10.9.49 | 4.5.0.7, 4.5.3.53, 4.6.0.196, 4.6.1.163, 4.6.1.164, 4.6.3.44, 4.6.4.25, 4.7.1.77, 4.7.1.78, 4.8.1.46, 4.9.26.33, 4.9.27.19, 4.9.28.21, 4.9.33.4, 4.10.9.49 |
| WSO2/WSO2 Enterprise Integratorgeneric | >=6.6.0 <6.6.0.229 | 6.6.0.229 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.320 || >=5.11.0 <5.11.0.427 || >=6.0.0 <6.0.0.254 || >=6.1.0 <6.1.0.195 || >=7.0.0 <7.0.0.82 | 5.10.0.320, 5.11.0.427, 6.0.0.254, 6.1.0.195, 7.0.0.82 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.314 | 5.10.0.314 |
| WSO2/WSO2 Open Banking AMgeneric | >=2.0.0 <2.0.0.345 | 2.0.0.345 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.366 | 2.0.0.366 |
| WSO2/WSO2 Traffic Managergeneric | >=4.5.0 <4.5.0.38 || >=4.6.0 <4.6.0.4 || >=4.6.0 <4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
| WSO2/WSO2 Universal Gatewaygeneric | >=4.5.0 <4.5.0.38 || >=4.6.0 <4.6.0.4 || >=4.6.0 <4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.
Quoted source text, attributed separately from HOL analysis.