dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56336

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-12
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 5 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 an information disclosure vulnerability in the unauthenticated /private/sso/check-domain endpoint that returns internal org_id and provider_id values. Attackers can enumerate email domains to build mappings of domains to organization UUIDs and SSO provider identifiers, enabling reconnaissance against Capgo tenants.

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 an unauthenticated information disclosure vulnerability in the /private/sso/check-domain endpoint. This endpoint returns internal organization IDs and SSO provider identifiers when queried with email domains, allowing unauthenticated attackers to enumerate domains and map them to organization UUIDs and SSO configurations for reconnaissance purposes.

MitigationUpgrade Capgo to version 12.128.2 or later to patch the vulnerability, or implement authentication and authorization controls on the /private/sso/check-domain endpoint to prevent unauthenticated access to sensitive identifier data.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
    Locate Capgo in your environment by checking for the Capgo service, application, or web server hosting it.
    Affected if Capgo is installed and running in the environment.
  2. Check Capgo version
    Determine the installed version of Capgo by inspecting the application metadata, package.json, container image tags, or the application's version endpoint if available.
    Affected if The installed version is earlier than 12.128.2.
  3. Verify endpoint accessibility
    Attempt an HTTP GET request to the /private/sso/check-domain endpoint without providing any authentication credentials.
    Affected if The endpoint responds without requiring authentication.
  4. Test for information disclosure
    Send an HTTP request to /private/sso/check-domain with a query parameter containing an email domain (such as ?domain=example.com) and examine the response.
    Affected if The response returns internal organization UUIDs, SSO provider identifiers, or other sensitive configuration data associated with the provided domain.
  5. Confirm unauthenticated enumeration
    Repeat the request with different email domains without authentication to verify that organization IDs and SSO details can be enumerated.
    Affected if Different domains return different organization identifiers without any authentication required.

You are affected if Capgo version is earlier than 12.128.2 AND the /private/sso/check-domain endpoint is accessible without authentication and returns organization UUIDs or SSO provider identifiers when queried with email domains.

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 patch the vulnerability, or implement authentication and authorization controls on the /private/sso/check-domain endpoint to prevent unauthenticated access to sensitive identifier data.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. Identify the currently installed Capgo version by checking the application or package.json
  2. Upgrade Capgo to version 12.128.2 or later to resolve the information disclosure vulnerability
  3. After upgrading, verify that the /private/sso/check-domain endpoint no longer returns org_id and provider_id values for unauthenticated requests
  4. If self-hosted, ensure the deployment pulls the updated container or package containing the fix

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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