CVE-2026-56223: Capgo account takeover via cross-domain SSO identity merge

CVE-2026-56223 · Severity: high · CVSS 8.7 · Published 2026-06-24

Capgo, a platform for managing app updates and deployments, suffered from a flaw in how it handles Single Sign-On (SSO) logins. An attacker with administrative access to their own enterprise account could use a malicious identity provider to impersonate any other user on the platform. This allows the attacker to take full control of victim accounts, gaining access to sensitive application data, organizational settings, and connected devices.

Technologies: Capgo. Vendors: Capgo.

Quick answers

Is CVE-2026-56223 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-56223 being exploited in the wild.
How severe is CVE-2026-56223?
High severity, with a CVSS score of 8.7, published 24 June 2026.
Which products and versions are affected?
Capgo < 12.128.2.
Is there a fix for CVE-2026-56223?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-56223 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-56223?
Check whether you run Capgo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in the `provision-user.ts` endpoint of Capgo allows for cross-domain account takeover via improper SSO identity merging. The root cause is a failure to validate that the authenticating SSO provider is authorized for the victim's email domain during the account merge process. An attacker with enterprise organization admin privileges can configure a malicious Identity Provider (IdP) to forge SAML assertions containing a victim's email address. When the attacker authenticates, the system identifies an existing account with that email and merges the attacker's SSO identity into the victim's account without verifying domain ownership. This grants the attacker full access to the victim's profile, organizations, and data. The issue is fixed in version 12.128.2.

Affected products

  • Capgo Capgo < 12.128.2

Timeline

  • 2026-05-07: advisory: GitHub Security Advisory published
  • 2026-06-24: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.