CVE-2026-53868
Description
Capgo before 12.128.2 allows unverified email registration and deletion, locking legitimate users out for 30 days.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Capgo before 12.128.2 allows unverified email registration and deletion, locking legitimate users out for 30 days.
Vulnerability
Capgo versions before 12.128.2 contain a denial of service vulnerability where the application does not require email verification before allowing sensitive account lifecycle actions. An attacker can register an account using any arbitrary email address without verifying ownership. The system reserves the email as a unique identifier and permits account deletion, placing the account into a 30-day pending deletion state. This locks the email address, preventing the legitimate owner from registering or accessing the platform [1][2].
Exploitation
An attacker with network access and no authentication can exploit this by registering an account with a victim's email address (no verification needed) and then initiating account deletion. The attacker does not need to control the email inbox. The victim's email becomes locked in a pending deletion state for 30 days [1].
Impact
During the 30-day lockout, the legitimate email owner cannot register a new account (system reports "User Already Exists"), cannot use password reset to regain normal access, and is redirected to an account-disabled page. The victim must contact support to restore access. This constitutes a denial of service against the legitimate user, with potential for mass lockouts and business disruption [1][2].
Mitigation
The vulnerability is fixed in Capgo version 12.128.2. Users should upgrade to this version or later. No workaround is documented; affected users must contact support to manually restore locked accounts [1][2].
AI Insight generated on Jun 12, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.