Unrated

Cap-go account takeover via unverified email registration and 2FA binding

IdentifiersCVE-2026-56081CWE-287

CVE-2026-56081 is an authentication logic flaw in Cap-go before 12.128.2. The application allows an attacker to register an account using a victim's email address before that email address has been verified. The attacker can then enable two-factor authentication on the pre-registered account, causing the account identity associated with the victim's email to remain under attacker control. This breaks the intended binding between email ownership and account ownership, enabling takeover of an account claimed under the victim's identity. The flaw affects the registration and authentication flow rather than a memory-safety issue or cryptographic weakness.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to control an account associated with the victim's email address, read and modify the account's state, and enforce organization-level policies through that account. The legitimate user can be denied access to the account tied to their own email address, resulting in account takeover, unauthorized administrative or policy actions, and loss of availability for the rightful user. Available scoring information indicates high confidentiality, integrity, and availability impact.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict or disable self-service registration paths that allow account creation with unverified email addresses, and prevent 2FA enrollment or other account-hardening actions until email verification is complete. Review existing accounts for cases where email addresses were bound prior to verification, especially where 2FA was enabled immediately after registration, and reset affected accounts through an out-of-band identity verification process. Strengthening email verification and registration security controls is also recommended.

Remediation

Patch, then assume compromise.

Upgrade Cap-go to version 12.128.2 or later. In addition, ensure the registration flow does not grant durable account control or permit security-sensitive actions such as enabling 2FA until email ownership has been verified. Review account binding, identity proofing, and registration logic to ensure unverified email addresses cannot be used to establish or retain control over accounts.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Cap-goCap-Goapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

6 SOURCESView more in app

cvefeed high severityNews

Jun 19, 2026

CVE-2026-56081 - Cap-go - Account Lockout via 2FA Misconfiguration on Unverified Email

An authentication logic flaw in Cap-go before version 12.128.2 that allows account takeover and lockout by pre-registering a victim's email before verification and enabling 2FA on the attacker-controlled account.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-56081

NVD

nvd.nist.gov/vuln/detail/CVE-2026-56081

MITRE CWE · CWE-287

cwe.mitre.org