CVE-2026-55216
Deferred Deferred - Pending Action

Social Account Linking Vulnerability in Logto

Vulnerability report for CVE-2026-55216, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-20

Last updated on: 2026-11-20

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-20
Last Modified
2026-11-20
Generated
2026-11-20
AI Q&A
2026-11-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
logto logto to 1.46.0 (exc)
logto logto to 1.43.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-345 The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Logto versions prior to 1.46.0 allows an attacker to link a social identity to a victim's account by exploiting unverified email addresses returned by OAuth 2.0 or Azure AD connectors. The attacker can then sign in as the victim.

Impact Analysis

If you use Logto with affected OAuth 2.0 or Azure AD connectors, an attacker could gain unauthorized access to your account by linking their social identity to yours. This could lead to data breaches or account takeover.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR's data protection principles and HIPAA's security requirements for safeguarding protected health information.

Mitigation Strategies

Upgrade to Logto version 1.46.0 or later to enable the opt-in email synchronization control in the standard OAuth 2.0 connector. For Azure AD connector, ensure version 1.43.0 or later is used and enable the equivalent opt-in control. These controls must be manually enabled as they preserve existing behavior by default.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-55216. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...