HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2024 6832 account lockout failure via secondary user store
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Contribute to HOL
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 5.9CVE-2024-6832

Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force AttacksCVE-2024-6832

Answer in brief

CVE-2024-6832 records a Medium severity (CVSS 5.9) 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.

Published Aug 6, 2026Updated Oct 27, 2026Source checked Nov 4, 2026First seen by HOL Aug 6, 2026Material review Oct 27, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.9
Exploitation
Not marked as known exploited
Affected software
33 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.9. 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 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.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:a:wso2:api_control_plane:4.5.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_control_plane:4.6.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:3.1.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:3.2.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:3.2.1:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:4.1.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:4.2.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:4.3.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:4.4.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:4.5.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:api_manager:4.6.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:identity_server:5.10.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:identity_server:5.11.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:identity_server:6.0.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:identity_server:6.1.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:identity_server:7.0.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:open_banking_am:2.0.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:open_banking_iam:2.0.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:traffic_manager:4.5.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:traffic_manager:4.6.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:universal_gateway:4.5.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:wso2:universal_gateway:4.6.0:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed 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.54.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.43.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.494.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.2296.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.825.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.3145.10.0.314
WSO2/WSO2 Open Banking AMgeneric>=2.0.0 <2.0.0.3452.0.0.345
WSO2/WSO2 Open Banking IAMgeneric>=2.0.0 <2.0.0.3662.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.54.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.54.5.0.38, 4.6.0.4, 4.6.0.5

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for WSO2/WSO2 API Control Plane, WSO2/WSO2 API Manager, WSO2/WSO2 Carbon User Manager Kernel.
  2. 2Review the reported fix. Source-reported solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/#solution

Evidence timeline and material changes

  1. Published upstream

    Aug 6, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 27, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 6, 2026

Sources and claim methodology

  • Source referencesecurity.docs.wso2.com
Upstream source description

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.

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-693
Source
CVE List V5
Source checked
Nov 4, 2026
References
1 linked source
Open source record