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-288

CVE-2026-56073 is an authentication bypass vulnerability affecting Cap-go versions prior to 12.128.2. The flaw is in the OTP-based email verification workflow. According to the provided content, an attacker can intercept OTP verification requests and manipulate HTTP responses so that verification is falsely treated as successful. This allows the attacker to bypass the intended email verification control during the OTP verification process. The issue indicates insufficient server-side enforcement or trust in client- or transit-modifiable verification state during the authentication/verification flow.

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 in the OTP workflow. The provided content states this can enable unauthorized activation of two-factor authentication and can ultimately result in account takeover. The vulnerability is described as remotely exploitable and critically severe.

Mitigation

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

If immediate patching is not possible, reduce exposure by hardening server-side OTP verification and auditing the email verification flow to ensure no client-controlled or interceptable response state can determine success. Review and restrict any logic that trusts modified HTTP responses for verification outcomes. Monitor for anomalous 2FA enablement events and suspicious account changes until the fixed version can be deployed.

Remediation

Patch, then assume compromise.

Upgrade Cap-go to version 12.128.2 or later. Apply the vendor security patch for this issue. Based on the provided content, remediation should also include correcting the OTP verification workflow so verification success is determined exclusively by trusted server-side validation, and reviewing response-handling logic to ensure manipulated HTTP responses cannot cause the application to mark verification as successful.
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.