CVE-2026-55377
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| logto-io | logto | < 1.41.0 | affected |
Weaknesses
- CWE-287: CWE-287: Improper Authentication
References
- https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j
- https://github.com/logto-io/logto/pull/9110
- https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74
- https://github.com/logto-io/logto/releases/tag/v1.41.0
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.