Logto account takeover via social account linking
Affects Logto when the OAuth 2.0 or Azure AD social connector is used with a provider that does not verify email addresses or lets users set email freely, and account linking is enabled. Fixed in 1.46.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.46.0
- Who is exposed
- Specific setups only
Summary
Logto's social account linking in the standard OAuth 2.0 and Azure AD connectors can trust an unverified email address from the identity provider, letting an attacker with a low-privilege login link their own social identity to a victim's existing account and sign in as that victim. The attack can be carried out remotely over the network and needs no action from the victim.
Written by a model
Original 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.
Who should check
Teams running Logto 1.45.0 or earlier with the OAuth 2.0 or Azure AD social connector against providers that do not verify emails
Not fixed by: Upgrading alone does not remove the exposure; disableEmailSync must also be enabled.
“If you use the OAuth 2.0 or Azure AD connector with a provider that does not verify email addresses”
What to do
Check whether your setup matches what the bug needs.
Standard OAuth 2.0 or Azure AD social connector used with a provider that does not verify email addresses or lets users set email freely Social sign-in matches an existing account by email and account linking is enabledUpgrade to a fixed version: 1.46.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-55216 (Logto: Account takeover via email_verified bypass in social account linking (Azure AD, OAuth2 connectors)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-55216 (entry last updated 2026-11-20):
Affected:
- logto-io logto: fixed in 1.46.0
Fixed versions: 1.46.0.
Conditions (all must be true for the bug to be hit):
- Standard OAuth 2.0 or Azure AD social connector used with a provider that does not verify email addresses or lets users set email freely (source: https://github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7)
- Social sign-in matches an existing account by email and account linking is enabled (source: https://github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-55216 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55216 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7
- https://github.com/logto-io/logto/pull/9858
- https://github.com/logto-io/logto/commit/1b03993a59c627ae83f0c892d76988ca056208b0
- https://github.com/logto-io/logto/releases/tag/v1.46.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-55216
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-55216"}.Affected versions
- logto-io logtofixed in 1.46.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · logto-io/logto · Advisory GHSA-gc94-xqg8-v8r7 |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55216 |
| Other links 3 | |
| Repository | GitHub · logto-io/logto · Pull request #9858 |
| Repository | GitHub · logto-io/logto · Commit 1b03993a |
| Repository | GitHub · logto-io/logto · Release v1.46.0 |
Questions about CVE-2026-55216
Is CVE-2026-55216 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A social sign-in that matches an existing account by email links the social identity to that account and signs the user in. An attacker who presents a social identity carrying a victim's email, without owning that mailbox, can link it to the victim's account and sign in as the victim.
Source: github.com
Which versions are affected by CVE-2026-55216?
logto: before 1.46.0.
Source: cve.now feed data
Am I affected, and how do I check?
Logto installations using the standard OAuth 2.0 or Azure AD social connector with a provider that does not verify email addresses or lets users set email freely, with account linking enabled. Check the installed Logto version against 1.46.0 and whether these connectors and account linking are in use.
Source: github.com
How do I fix CVE-2026-55216?
Upgrade Logto to 1.46.0 or later.
Source: github.com
Related
- CVE-2026-63188logto-tunnel serves files outside --experience-path via path traversal
- CVE-2026-56739Logto: SSRF via Webhooks and Custom OAuth2 Connector UserInfo Endpoint
- CVE-2026-55789Logto: SAML IdP injects user-controlled profile attributes raw into signed assertions, allowing privilege escalation at relying Service…
- CVE-2026-82263Logto Server-Side Request Forgery via OIDC SSO Connector Issuer URL
- CVE-2026-82262Logto Server-Side Request Forgery via webhook test endpoint
- CVE-2026-55377Logto: Account Center MFA management step-up bypass via WebAuthn registration verification
No corrections so far. Something wrong on this page? Report an error.