dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-56223

HIGH · 8.7 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 →
93/100
Remediation priority · Urgent
Remotely reachable 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 cross-domain SSO account takeover vulnerability in the provision-user endpoint that allows attackers to merge arbitrary victim accounts based on email match without validating SSO provider domain authorization. An attacker with enterprise org admin access and a malicious IdP can forge SAML assertions containing victim email addresses to trigger account merge and gain full access to victim accounts, organizations, and data.

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 cross-domain SSO account takeover vulnerability in the provision-user endpoint. The endpoint fails to validate SSO provider domain authorization when merging accounts based on email matching. An attacker with enterprise org admin access and a malicious IdP can forge SAML assertions containing victim email addresses to trigger unauthorized account merges and gain full access to victim accounts, organizations, and data.

MitigationUpgrade to Capgo 12.128.2 or later. Additionally, implement proper SSO provider domain authorization validation in the provision-user endpoint to ensure only legitimate domain-authorized IdPs can trigger account merges.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 and version
    Locate the Capgo application or service in your environment and determine the installed version number. This may be visible in the application UI, package.json, a running service version, or your software bill of materials (SBOM).
    Affected if The installed version is Capgo and is below version 12.128.2.
  2. Confirm SSO/SAML integration is enabled
    Check whether the Capgo instance has any SAML-based Single Sign-On (SSO) or OpenID Connect (OIDC) identity provider (IdP) integrations configured. This is typically found in organization settings, authentication settings, or identity provider configuration pages.
    Affected if SSO or SAML integration is active and configured for the organization.
  3. Verify enterprise organization admin access exists
    Examine whether the Capgo organization has enterprise features enabled and whether any user accounts possess organization-level administrator privileges. Check user role assignments in the admin or user management console.
    Affected if Enterprise organization and org admin roles are defined in the system.
  4. Inspect provision-user endpoint configuration
    Review the configuration or access logs related to the provision-user endpoint. Determine whether domain validation for SSO providers is enforced before account merging based on email matching. Look for settings controlling which IdPs can trigger account merges.
    Affected if The provision-user endpoint allows account merges without validating that the SSO provider is authorized for the target email domain.

You are likely affected if you are running Capgo version below 12.128.2 with SSO/SAML integration enabled and enterprise organization admin accounts configured in your environment.

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 to Capgo 12.128.2 or later. Additionally, implement proper SSO provider domain authorization validation in the provision-user endpoint to ensure only legitimate domain-authorized IdPs can trigger account merges.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. Identify the current Capgo installation version by checking the application or deployment configuration
  2. Review the Capgo release notes or changelog for version 12.128.2 to understand the security fix
  3. Plan the upgrade process, ensuring backup of current configuration and data
  4. Upgrade Capgo to version 12.128.2 or later following the standard upgrade procedure for your deployment method
  5. After upgrade, verify the SSO/SAML configuration and test the provision-user endpoint to confirm the vulnerability is remediated
  6. Audit existing user accounts for any unauthorized merges that may have occurred prior to the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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