Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Unrated

Authentication Bypass in Cap-go OTP Verification

IdentifiersCVE-2026-56073CWE-345

CVE-2026-56073 is an authentication bypass vulnerability affecting Cap-go versions prior to 12.128.2. The flaw exists in the OTP-based email verification workflow, where an attacker can intercept OTP verification requests and manipulate HTTP responses so that verification is incorrectly treated as successful. As described in the available content, this allows bypass of email verification controls and undermines the integrity of the OTP verification process. The issue appears to stem from improper trust in client-observable or modifiable response handling during verification rather than robust server-side validation.

Share:
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.

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 an attacker to bypass email verification, enable 2FA without proper authorization, and potentially take over affected accounts. The provided content characterizes the issue as remotely exploitable and critical, with high impact to confidentiality, integrity, and availability.

Mitigation

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

If immediate patching is not possible, harden server-side OTP verification and response handling so that verification state cannot be altered by tampering with intercepted traffic. Validate OTP completion exclusively on the server, audit email verification and 2FA enrollment flows for trust-boundary violations, and monitor for anomalous or unauthorized 2FA enablement events until the fixed version is deployed.

Remediation

Patch, then assume compromise.

Upgrade Cap-go to version 12.128.2 or later. Apply vendor security patches and review the OTP verification implementation to ensure verification success is determined exclusively by trusted server-side validation rather than modifiable HTTP response content or client-side state.
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.

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.
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 activity6

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