dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-55377

HIGH · 8.1 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Logto versions prior to 1.41.0 contain an authentication bypass in the Account Center step-up verification. The system incorrectly accepts any active verification record belonging to the current user with isVerified=true as valid identity proof. An attacker with a valid Account API bearer token can create and verify a WebAuthn registration record for binding a new passkey, then reuse that record via the logto-verification-id header to bypass identity verification and manage MFA factors without proving possession of existing credentials.

MitigationUpgrade Logto to version 1.41.0 or later. After upgrading, audit all MFA configurations and verify that existing authentication flows function correctly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Logto version
    Query the Logto instance metadata endpoint (such as /.well-known/openid-configuration or the admin API /api/status) to retrieve the server version. Compare this version against the affected range: versions prior to 1.41.0.
    Affected if The installed version is 1.40.x or earlier.
  2. Verify Account API accessibility
    Confirm that the Account API endpoint (typically /api/settings/account) accepts requests with a valid bearer token. The vulnerability requires a valid Account API bearer token to exploit.
    Affected if The Account API accepts authenticated requests without additional step-up verification.
  3. Confirm WebAuthn/passkey registration is enabled
    Inspect the Logto MFA configuration to determine if WebAuthn/passkey registration is allowed. Check whether the passkey binding feature is active in the authentication settings.
    Affected if WebAuthn/passkey registration is enabled and users can create new verification records.
  4. Review verification records for isVerified=true status
    Query the Logto database or API for verification records where isVerified=true exists for user accounts. The flaw allows reuse of any such record via the logto-verification-id header.
    Affected if Multiple active verification records with isVerified=true exist for the same user beyond the current authentication session.
  5. Audit recent MFA factor modifications
    Review authentication and MFA management logs for unexpected changes to MFA factors (such as adding new passkeys or authenticator apps) that occurred without proper step-up verification.
    Affected if MFA factors were added or modified using verification records that should have required additional identity proof.

The environment is affected if Logto version is prior to 1.41.0 and the Account API with valid bearer tokens can create/verify WebAuthn registration records that are then reused to bypass step-up verification for MFA management.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Logto to version 1.41.0 or later. After upgrading, audit all MFA configurations and verify that existing authentication flows function correctly.

Recommended fix High confidence

1.41.0

  1. Identify the current Logto version in use by checking package.json or the deployed Docker image tag
  2. Upgrade Logto to version 1.41.0 or later using the appropriate method (npm package update, Docker image pull, or repository update)
  3. Verify the upgrade by checking that the version number matches 1.41.0 or higher
  4. Test the Account Center step-up authentication flow to confirm the fix is working correctly
  5. Ensure any automated tests or CI/CD pipelines are updated to use the new version
Caveat Review Logto 1.41.0 release notes for any potential breaking changes in your integration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55377 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data