What’s Vulnerable › Vulnerabilities

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

• Severity: high (CVSS 8.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-07-10 · updated 2026-10-25
• Weakness: CWE-287

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.

Affected products

• logto-io logto: before 1.41.0

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

Get alerted when CVE-2026-55377 or the next vulnerability affects your stack