CVE-2026-55377 Logto: Account Center MFA management step-up bypass via WebAuthn registration verification
Attackers can bypass MFA step-up checks in Logto's Account Center to manage MFA factors without proving possession of existing credentials.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-55377?
CVE-2026-55377 is a high-severity authentication bypass vulnerability in logto-io logto, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2026-55377?
How do I fix CVE-2026-55377?
No fix has been published for CVE-2026-55377 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-55377 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55377 exists.
Sources
Also known as GHSA-q4h3-38gc-4p4j.