dbcve.org
CWE-703Weakness · CWE-703

CVE-2026-56338

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Capgo before 12.128.2 contains a denial of service vulnerability in the /auth/v1/otp endpoint that prevents email verification for two-factor authentication due to captcha validation failures. Authenticated users cannot complete 2FA enrollment as the backend consistently returns HTTP 500 errors with captcha verification process failed messages, blocking access to security controls.

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 confidence

Capgo before version 12.128.2 contains a denial of service vulnerability in the /auth/v1/otp endpoint. The captcha validation logic fails consistently, causing the backend to return HTTP 500 errors with 'captcha verification process failed' messages. This prevents authenticated users from completing 2FA enrollment, blocking access to a critical security control.

MitigationUpgrade Capgo to version 12.128.2 or later to resolve the captcha validation failure. If immediate upgrade is not possible, temporarily disable captcha requirements for the otp endpoint as a compensating control while planning the upgrade.

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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Capgo installation and version
    Run 'capgo --version' or check package.json for '@capgo/api' or similar Capgo package, or check the running service version via API health endpoint
    Affected if Capgo version is present and is below 12.128.2
  2. Confirm /auth/v1/otp endpoint is exposed
    Check application routing configuration or API gateway rules for routes matching /auth/v1/otp
    Affected if The /auth/v1/otp endpoint is accessible in the environment
  3. Verify captcha is enabled for OTP enrollment
    Review Capgo configuration files or environment variables for captcha settings related to OTP/2FA enrollment flow
    Affected if Captcha validation is configured and enabled for the otp endpoint
  4. Test captcha validation on the otp endpoint
    Attempt to complete 2FA enrollment through the /auth/v1/otp endpoint and observe if HTTP 500 errors with 'captcha verification process failed' are returned
    Affected if The endpoint returns 500 errors with captcha verification failure messages

If Capgo version is below 12.128.2 and the /auth/v1/otp endpoint with captcha is in use, the environment is affected by this denial of service vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Capgo to version 12.128.2 or later to resolve the captcha validation failure. If immediate upgrade is not possible, temporarily disable captcha requirements for the otp endpoint as a compensating control while planning the upgrade.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the currently installed Capgo version by checking the application's package.json, version file, or deployment configuration
  2. 2. If the installed version is before 12.128.2, plan an upgrade to version 12.128.2 or later
  3. 3. Review Capgo's release notes or changelog between your current version and 12.128.2 for any required migration steps
  4. 4. Test the upgrade in a staging environment before deploying to production
  5. 5. Verify that the /auth/v1/otp endpoint now processes captcha validation correctly and 2FA enrollment works as expected
  6. 6. Deploy the upgraded version to production
Caveat Review release notes for potential breaking changes between your current version and 12.128.2

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56338 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56338 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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