CVE-2026-55216 json
Logto: Account takeover via email_verified bypass in social account linking (Azure AD, OAuth2 connectors)
published 15d ago modified 1h ago also GHSA-gc94-xqg8-v8r7 , EUVD-2026-131704
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository logto-io/logto. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.46.0, social account linking can use an unverified email returned by the standard OAuth 2.0 or Azure AD connector to select an existing local account. When findSocialRelatedUser matches a victim's email and a request to POST /api/experience/identification enables linkSocialIdentity, an attacker who controls that unverified provider email can link an attacker-controlled social identity to the victim account and sign in as the victim. The issue applies when the provider does not verify email ownership or allows the value to be set freely; Google, GitHub, and default OIDC connector behavior is not affected because those paths expose only verified email. Version 1.46.0 adds an opt-in email synchronization control to the standard OAuth 2.0 connector, while the Azure AD connector has offered an equivalent opt-in control since version 1.43.0. These controls preserve existing behavior by default, so administrators must enable them on affected connectors. A configurable mitigation is available in version 1.46.0.
Patch / fix
- github.com/logto-io/logto@1b03993 commit
- github.com/logto-io/logto#9858 pull request
- github.com/logto-io/logto/releases/tag/v1.46.0 release
Is CVE-2026-55216 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected products
- logto-io logto
Classification
References
Sources
- CVE List CVE-2026-55216
- NVD CVE-2026-55216
- Maintainer advisory GHSA-gc94-xqg8-v8r7
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of logto-io/logto published their own advisory on GitHub. Reviewed sources take precedence over it.