dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-56237

CRITICAL · 9.1 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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 broken authentication vulnerability in its API key generation mechanism. API keys are exposed in frontend requests, and the backend fails to validate that keys are securely generated and bound to the authenticated user. An attacker can tamper with the API key parameter in the generation request and supply arbitrary values, generating custom API keys without proper authorization, which can lead to unauthorized access to protected endpoints.

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 · high confidence

Capgo before 12.128.2 has a broken authentication vulnerability in its API key generation mechanism. The backend accepts arbitrary API key values supplied by clients in requests instead of generating keys server-side, and fails to validate that generated keys are bound to the authenticated user. This allows attackers to create valid API keys with arbitrary values, granting unauthorized access to protected endpoints.

MitigationFix the API key generation to be performed server-side with proper cryptographic randomness, implement validation that keys are bound to the authenticated user identity, and reject any client-supplied key values in the generation request.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 version
    Locate the installed Capgo package or application and retrieve its version number using package manager queries, application metadata, or version display commands
    Affected if The version is lower than 12.128.2 (e.g., 12.128.1, 12.127.x, or earlier)
  2. Inspect API key generation request behavior
    Capture or review API requests sent to the key generation endpoint and observe whether the client is able to supply a custom key value in the request payload rather than receiving a server-generated key in the response
    Affected if The API accepts and processes client-supplied key values in the key generation request instead of rejecting them
  3. Verify key-user binding validation
    Test the API key generation flow by authenticated users and examine whether the backend validates that generated keys are associated with the requesting user's identity, or if it accepts any key regardless of user context
    Affected if The system does not validate that generated API keys are bound to the authenticated user identity, or allows keys to be created without proper user association
  4. Confirm server-side key generation is enforced
    Analyze the API key creation process to determine if keys are generated server-side with proper cryptographic randomness, or if the backend blindly accepts client-provided key values
    Affected if API keys are not generated server-side with cryptographic randomness but instead accept arbitrary client-supplied values

A Capgo installation is affected if it runs a version before 12.128.2 and the API key generation mechanism accepts client-supplied key values without server-side generation or user-binding validation.

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

Fix the API key generation to be performed server-side with proper cryptographic randomness, implement validation that keys are bound to the authenticated user identity, and reject any client-supplied key values in the generation request.

Recommended fix Moderate confidence

Capgo 12.128.2

  1. 1. Identify current Capgo installation version
  2. 2. Upgrade Capgo to version 12.128.2 or later
  3. 3. After upgrade, verify API key generation now properly binds keys to authenticated users
  4. 4. Rotate any API keys that may have been generated during the vulnerable period

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56237 — 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-56237 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