CVE-2026-56215
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 · uneditedCapgo 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.
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 confidenceIn Capgo before version 12.128.12, authenticated users can modify their public.users.email field to arbitrary values. The SSO provisioning endpoint uses this email as a trusted key for account merging. An attacker can set their email to a victim's corporate SSO email, causing the provision-user endpoint to merge the victim's SSO identity into the attacker's existing account, resulting in account takeover.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo versionQuery the installed Capgo version through the application admin panel, package manager, or API endpoint that returns version information. Compare the version number to the affected range (before 12.128.12).Affected if Running any version of Capgo prior to 12.128.12
-
Verify email field mutabilityCheck the user profile settings or public.users table configuration to determine if the email field allows authenticated users to modify their own email address. Inspect the data model or application settings that control field editability.Affected if Users can modify their own email to arbitrary values without administrative approval or ownership verification
-
Confirm SSO integration is activeReview the Capgo authentication configuration to determine if any SAML, OIDC, or other SSO provider is connected and provisioning users through the SSO endpoint.Affected if SSO authentication is enabled and the provision-user endpoint is accessible
-
Audit recent account merge eventsReview application logs, audit trails, or user account records to identify any instances where accounts were merged, particularly where the merged identity originated from SSO and the primary account had a different email than the SSO email.Affected if Account merge events exist where the pre-existing account email differs from the SSO identity email being merged
You are affected if running Capgo before 12.128.12 with SSO enabled and a mutable email field allows attackers to trigger unauthorized account merges.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Capgo 12.128.12 or later. Until then, disable or add verification requirements to the mutable email field and implement proper email ownership validation before SSO account merging.
12.128.12 or later
- 1. Identify the current installed version of Capgo by checking the application configuration or package.json
- 2. Upgrade Capgo to version 12.128.12 or later by updating the dependency in your package.json or lock file
- 3. Run the appropriate package manager update command (e.g., npm update @capgo/[package-name] or yarn upgrade @capgo/[package-name])
- 4. Verify the upgrade was successful by checking the installed version matches 12.128.12 or higher
- 5. Test the SSO authentication flow to confirm the account merge vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56215 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56215 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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