PatchTheCVECVE-2024-6832: The account locking mechanism fails to trigger when secondary user stores are inaccessible
34
Routine
MEDIUM 5.9REMOTEDOWNGRADEDOWNGRADEDOWNGRADE
CVE-2024-6832 is a medium-severity flaw (CVSS 5.9) affecting api control plane, api manager, identity server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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 seconda
Why this priority
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.9 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 65%) |
| CISA exploited list | No |
| Weakness | CWE-693 |
| Published | 2026-08-06 |
| Last modified | 2026-08-09 |
Last updated 2026-08-09 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
wso2 api control plane DOWNGRADE
Affected: 4.5.0 · 4.6.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy api-control-plane || rpm -q api-control-plane || api-control-plane --version
2. No fixed release: DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison api-control-plane
sudo apt install api-control-plane=<VERSION_BEFORE_4.5.0>
sudo apt-mark hold api-control-plane
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-control-plane
sudo dnf downgrade api-control-plane-<VERSION_BEFORE_4.5.0>
sudo dnf versionlock add api-control-plane
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 api manager DOWNGRADE
Affected: 3.1.0 · 3.2.0 · 3.2.1 · 4.1.0 · 4.2.0 · 4.3.0 · 4.4.0 · 4.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.1.0
1. Check installed version
apt-cache policy api-manager || rpm -q api-manager || api-manager --version
2. No fixed release: DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)
apt-cache madison api-manager
sudo apt install api-manager=<VERSION_BEFORE_3.1.0>
sudo apt-mark hold api-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-manager
sudo dnf downgrade api-manager-<VERSION_BEFORE_3.1.0>
sudo dnf versionlock add api-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 identity server DOWNGRADE
Affected: 5.10.0 · 5.11.0 · 6.0.0 · 6.1.0 · 7.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.10.0
1. Check installed version
apt-cache policy identity-server || rpm -q identity-server || identity-server --version
2. No fixed release: DOWNGRADE to a release before 5.10.0 (Debian / Ubuntu)
apt-cache madison identity-server
sudo apt install identity-server=<VERSION_BEFORE_5.10.0>
sudo apt-mark hold identity-server
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list identity-server
sudo dnf downgrade identity-server-<VERSION_BEFORE_5.10.0>
sudo dnf versionlock add identity-server
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 identity server as key manager DOWNGRADE
Affected: 5.10.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.10.0
1. Check installed version
apt-cache policy identity-server-as-key-manager || rpm -q identity-server-as-key-manager || identity-server-as-key-manager --version
2. No fixed release: DOWNGRADE to a release before 5.10.0 (Debian / Ubuntu)
apt-cache madison identity-server-as-key-manager
sudo apt install identity-server-as-key-manager=<VERSION_BEFORE_5.10.0>
sudo apt-mark hold identity-server-as-key-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list identity-server-as-key-manager
sudo dnf downgrade identity-server-as-key-manager-<VERSION_BEFORE_5.10.0>
sudo dnf versionlock add identity-server-as-key-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 open banking am DOWNGRADE
Affected: 2.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy open-banking-am || rpm -q open-banking-am || open-banking-am --version
2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison open-banking-am
sudo apt install open-banking-am=<VERSION_BEFORE_2.0.0>
sudo apt-mark hold open-banking-am
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list open-banking-am
sudo dnf downgrade open-banking-am-<VERSION_BEFORE_2.0.0>
sudo dnf versionlock add open-banking-am
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 open banking iam DOWNGRADE
Affected: 2.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy open-banking-iam || rpm -q open-banking-iam || open-banking-iam --version
2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison open-banking-iam
sudo apt install open-banking-iam=<VERSION_BEFORE_2.0.0>
sudo apt-mark hold open-banking-iam
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list open-banking-iam
sudo dnf downgrade open-banking-iam-<VERSION_BEFORE_2.0.0>
sudo dnf versionlock add open-banking-iam
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-6832?
api control plane: downgrade or apply the listed mitigation; api manager: downgrade or apply the listed mitigation; identity server: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2024-6832 being exploited?
CVE-2024-6832 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-6832 affect?
CVE-2024-6832 affects api control plane, api manager, identity server. Severity is medium (CVSS 5.9). 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 repeate
How urgent is CVE-2024-6832?
Priority 34/100. Remotely exploitable, no login, no user action
Related CVEs
- CVE-2025-12737 HIGH 8.4 UPGRADE UPGRADE The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu
- CVE-2025-15039 CRITICAL 9.4 UPGRADE UPGRADE The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of a
- CVE-2025-13394 MEDIUM 5.4 UPGRADE UPGRADE The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-
- CVE-2026-5430 CRITICAL 10.0 EXPLOITED UPGRADE UPGRADE WSO2 Multiple Products Path Traversal Vulnerability
- CVE-2026-3416 MEDIUM 5.9 UPGRADE UPGRADE The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create