CVE-2026-55216
High 8.1No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
No EPSS score available
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-287, CWE-345
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/logto-io/logto/commit/1b03993a59c627ae83f0c892d76988ca056208b0 (opens in a new tab)
- https://github.com/logto-io/logto/pull/9858 (opens in a new tab)
- https://github.com/logto-io/logto/releases/tag/v1.46.0 (opens in a new tab)
- https://github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7 (opens in a new tab)