CVE-2026-55377 PUBLISHED

Logto: Account Center MFA management step-up bypass via WebAuthn registration verification

Assigner: GitHub_M
Reserved: 16.06.2026 Published: 10.07.2026 Updated: 10.07.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 8.1

Product Status

Vendor logto-io
Product logto
Versions
  • Version < 1.41.0 is affected

References

Problem Types

  • CWE-287: Improper Authentication CWE