CVE-2026-56215: Capgo - Account Merge via Poisoned public.users.email in SSO Provisioning

Published Jun 20, 2026
·
Updated

Capgo before 12.128.12 allows authenticated users to modify their mutable public.users.email to arbitrary addresses, which the SSO provisioning endpoint trusts as an account-merge key. Attackers can pre-position their account with a victim's corporate SSO email, causing the provision-user endpoint to merge the victim's SSO identity into the attacker-controlled account.

Affected Software

1 affected component
Capgo Capgo<12.128.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Capgo to a version that resolves this vulnerability.

    Fixed in 12.128.12
  2. Configuration

    Prevent authenticated users from modifying public.users.email or mark public.users.email as immutable; ensure the provisioning endpoint does not accept user-modified public.users.email as an account-merge key.

    Capgo SSO provisioning / public.users.email public.users.email (user-modifiable) = immutable / not trusted for account-merge
  3. Configuration

    Change the account-merge logic to rely on an immutable identifier from the SSO identity provider (for example the subject or a stable federated ID) rather than the public.users.email field supplied/owned by users.

    Capgo SSO provisioning account-merge key = use immutable SSO identifier (IdP-provided) instead of user-controlled email
  4. Compensating control

    Require server-side verification of any email used for account-merge (match against verified IdP assertion) or restrict account-merge operations to administrative or policy-controlled workflows until fixes are applied.

  5. Operational

    Audit recent provisioning and account-merge events to detect and remediate any accounts that may have been merged improperly; revert unauthorized merges and notify affected users and administrators.

Event History

Jun 20, 2026
CVE Published
via MITRE·12:14 AM
Data Sourced
via MITRE·12:14 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-56215?

CVE-2026-56215 has a high severity rating of 8.3.

2

How do I fix CVE-2026-56215?

To fix CVE-2026-56215, update Capgo to version 12.128.13 or later where the vulnerability is addressed.

3

What are the potential impacts of CVE-2026-56215?

CVE-2026-56215 allows attackers to merge accounts by modifying public.users.email to a victim's email, potentially leading to unauthorized access.

4

Who is affected by CVE-2026-56215?

Authenticated users of Capgo before version 12.128.13 can be affected by CVE-2026-56215.

5

How does CVE-2026-56215 exploit the system?

CVE-2026-56215 exploits the trust in the public.users.email field as an account-merge key in the SSO provisioning endpoint.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203