CVE-2026-55216: logto · Improper Authentication
Affects logtoSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 1.46.0 soon.
Data as of 20 Nov 2026, 17:59 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.1 |
|---|
- Patch
- Available – fixed in 1.46.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade logto to 1.46.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| logto-iologto | Affected
| Fixed in
|
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.
References
- github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7 (opens in a new tab)
- github.com/logto-io/logto/pull/9858 (opens in a new tab)
- github.com/logto-io/logto/commit/1b03993a59c627ae83f0c892d76988ca056208b0 (opens in a new tab)
- github.com/logto-io/logto/releases/tag/v1.46.0 (opens in a new tab)