8.1
HIGH CVSS 3.1
CVE-2026-55377
Logto: Account Center MFA management step-up bypass via WebAuthn registration verification
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.

INFO

Published Date :

July 10, 2026, 8:16 p.m.

Last Modified :

July 10, 2026, 8:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-55377 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
Solution
Update Logto to version 1.41.0 or later to fix the account center step-up check vulnerability.
  • Update Logto to version 1.41.0.
  • Verify Logto is updated to version 1.41.0.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-55377 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-55377 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-55377 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 10, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'logto-io', 'product': 'logto', 'versions': [{'status': 'affected', 'version': '< 1.41.0'}]}]
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
    Added CWE CWE-287
    Added Reference https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74
    Added Reference https://github.com/logto-io/logto/pull/9110
    Added Reference https://github.com/logto-io/logto/releases/tag/v1.41.0
    Added Reference https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.