CVE-2026-55377: CWE-287: Improper Authentication in logto-io logto
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.
AI Analysis
Technical Summary
Logto versions before 1.41.0 have an improper authentication vulnerability (CWE-287) where the Account Center step-up check accepts any active verification record with isVerified === true belonging to the current user. An attacker possessing a valid Account API bearer token could create and verify a WebAuthn registration verification record for binding a new passkey, then use this record in the logto-verification-id header to bypass authentication requirements. This allowed management of MFA factors without proving possession of an existing password, identifier, or MFA factor. The vulnerability is resolved in version 1.41.0.
Potential Impact
An attacker with a valid Account API bearer token can bypass authentication controls in the Account Center to manage MFA factors without needing to prove possession of existing credentials or MFA factors. This leads to a high impact on confidentiality and integrity, as unauthorized users could alter multi-factor authentication settings, potentially compromising account security. Availability is not affected.
Mitigation Recommendations
Upgrade to Logto version 1.41.0 or later, where this vulnerability is fixed. There is no indication of alternative mitigations or temporary fixes. Patch status is confirmed by the vendor advisory stating the issue is fixed in 1.41.0.
CVE-2026-55377: CWE-287: Improper Authentication in logto-io logto
Description
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.
CVSS v3.1
Score 8.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Logto versions before 1.41.0 have an improper authentication vulnerability (CWE-287) where the Account Center step-up check accepts any active verification record with isVerified === true belonging to the current user. An attacker possessing a valid Account API bearer token could create and verify a WebAuthn registration verification record for binding a new passkey, then use this record in the logto-verification-id header to bypass authentication requirements. This allowed management of MFA factors without proving possession of an existing password, identifier, or MFA factor. The vulnerability is resolved in version 1.41.0.
Potential Impact
An attacker with a valid Account API bearer token can bypass authentication controls in the Account Center to manage MFA factors without needing to prove possession of existing credentials or MFA factors. This leads to a high impact on confidentiality and integrity, as unauthorized users could alter multi-factor authentication settings, potentially compromising account security. Availability is not affected.
Mitigation Recommendations
Upgrade to Logto version 1.41.0 or later, where this vulnerability is fixed. There is no indication of alternative mitigations or temporary fixes. Patch status is confirmed by the vendor advisory stating the issue is fixed in 1.41.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T18:57:40.181Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a51500968715ace431e0bbf
Added to database: 07/10/2026, 20:03:21 UTC
Last enriched: 07/18/2026, 15:36:27 UTC
Last updated: 08/24/2026, 22:52:12 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.