---
id: CVE-2026-55377
title: 'Logto is the modern, open-source auth infrastructure for SaaS and AI apps'
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 Web…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'
cwe:
  - CWE-287
published: '2026-07-10'
updated: '2026-07-10'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-55377'
references:
  - url: >-
      https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74
    label: security-advisories@github.com
  - url: 'https://github.com/logto-io/logto/pull/9110'
    label: security-advisories@github.com
  - url: 'https://github.com/logto-io/logto/releases/tag/v1.41.0'
    label: security-advisories@github.com
  - url: 'https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j'
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.00464
epssPercentile: 0.37552
ingestedAt: '2026-07-11T20:15:26.544Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.