CVE-2026-56073
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCap-go before 12.128.2 contains an authentication bypass vulnerability in OTP verification that allows attackers to bypass email verification by modifying server responses. Attackers can intercept OTP verification requests and manipulate HTTP responses to falsely mark verification successful, enabling unauthorized 2FA enablement and account takeover.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCap-go before 12.128.2 has a critical authentication bypass in its OTP verification flow where the server trusts client-manipulated HTTP responses. Attackers can intercept verification requests and modify the server response to falsely indicate successful verification, bypassing email/2FA verification entirely and enabling account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Cap-go installed versionLocate the Cap-go package in your environment and retrieve its version number. This may be in package.json, a lock file, or the installed node_modules. Compare the version against the fixed release 12.128.2.Affected if The installed version is earlier than 12.128.2
-
Verify OTP verification is in useInspect your application configuration or codebase to determine whether the OTP/email verification feature provided by Cap-go is enabled for user authentication flows.Affected if OTP verification is enabled and the Cap-go version is vulnerable
-
Inspect OTP verification endpoint logicExamine the server-side code handling OTP verification requests. Look for the validation routine that checks whether an entered OTP code is valid. Determine if this validation relies on a response that could be intercepted and modified by a client.Affected if The verification logic accepts client-controlled responses without independent server-side validation of the OTP correctness
-
Test OTP flow for response manipulationDuring an OTP verification request, intercept the HTTP response from your server using a proxy tool. Modify the response body to indicate verification success (for example, changing a 'verified': false to 'verified': true or a similar success flag), then forward the modified response. Observe whether the application treats this manipulated response as a successful verification.Affected if The application accepts the manipulated response and grants access as if the OTP was verified
You are affected if Cap-go version is below 12.128.2 AND the OTP verification feature is enabled in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate to version 12.128.2 or later. Ensure OTP verification logic performs server-side validation that cannot be overridden by client-side response manipulation.
12.128.2 or later
- Upgrade Cap-go to version 12.128.2 or later to resolve the OTP verification bypass vulnerability
- After upgrading, verify that the OTP/email verification flow now properly validates server-side responses and cannot be manipulated via HTTP response modification
- Test that legitimate OTP verification still functions correctly for new user registrations
- Monitor for any signs of attempted exploitation prior to the upgrade (unauthorized 2FA enablement, suspicious account modifications)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data