CVE-2026-55377

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 3.1

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

EPSS

0.6% chance of exploitation in the next 30 days; higher than 47% of CVEs (scores of 2026-10-25)

CWE

CWE-287

Published

2026-07-10

Modified

2026-10-25

Record from

the NVD, synced 2026-10-25

References

• https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74
• https://github.com/logto-io/logto/pull/9110
• https://github.com/logto-io/logto/releases/tag/v1.41.0
• https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j
• https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j

Check your stackJSON