CVE-2026-55216 Details
Description
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.
A vulnerability in Logto's social account linking feature, specifically within the OAuth 2.0 and Azure Active Directory connectors, prior to version 1.46.0, can lead to unauthorized account access. The issue arises because these connectors may return unverified email addresses, which can be exploited to link a social identity to a local account without proper verification. When the linked email matches that of a victim's account, an attacker can gain access to the victim's account by signing in with the linked social identity. This vulnerability does not affect Logto's GitHub, Google, or default OpenID Connect connectors, as they only provide verified email addresses.
Logto version 1.46.0 introduces a configurable option to disable email synchronization for the OAuth 2.0 and Azure AD connectors. Administrators must review and adjust the settings on these connectors after upgrading to version 1.46.0.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 20, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/logto-io/logto/commit/1b03993a59c627ae83f0c892d76988ca056208b0 | [email protected] | Broken LinkSource CodeVendor |
| https://github.com/logto-io/logto/pull/9858 | [email protected] | Issue TrackingVendor |
| https://github.com/logto-io/logto/releases/tag/v1.46.0 | [email protected] | Release NotesVendor |
| https://github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7 | [email protected] | AdvisoryExploitRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-287 | Improper Authentication | [email protected] |
| CWE-345 | Insufficient Verification of Data Authenticity | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Logto | <= 1.45.0 (semver) |
CPE
Remediation
| |
Change History
1 change record found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 20, 2026 | New CVE Received | [email protected] |
Volerion