CVE-2026-55216
Logto: Account takeover via email_verified bypass in social account linking (Azure AD, OAuth2 connectors)
No exploitation reported by the sources we read.
- Published2026-11-20
- WeaknessCWE-287 · CWE-345
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-11-2017:49CVE publishedCNA
Versions per branch
Products declared by the CNA
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- logto-io logtoAffected
- = < 1.46.0no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-20
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-55216 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Published
- 2026-11-20
Frequently asked questions
What is CVE-2026-55216?
Is CVE-2026-55216 actively exploited?
What is the CVSS score for CVE-2026-55216?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
- CVE-2026-95645same week
- CVE-2026-95643same week
- CVE-2026-123633same weekNGINX ngx_http_v2_module vulnerability
- CVE-2026-123007same weekNGINX ngx_http_v2_module vulnerability
- CVE-2026-14492same week
- CVE-2026-132622same weekGearUP Hyperev WLAN Site Survey utils.lua get_wlan_sitesurvey os command injection
- CVE-2026-116449same weekOS Command Injection in Dell PowerStore SDNAS Enables Root Execution
- CVE-2026-116448same weekOS Command Injection in Dell PowerStore Enables Arbitrary Root Commands