---
id: CVE-2026-62317
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 email subaddressing blocklist in
  packages/core/src/libraries/sign-in-experience/email-blocklist-policy.ts used
  the attacker-controlled do…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-1333
published: '2026-08-19'
updated: '2026-09-09'
sourceUpdated: '2026-09-09T21:15:59.613'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-62317'
references:
  - url: >-
      https://github.com/logto-io/logto/commit/021381237511bc0d42f81d65df8b036b01f40547
    label: security-advisories@github.com
  - url: 'https://github.com/logto-io/logto/pull/9106'
    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-qp7j-c3q2-g739'
    label: security-advisories@github.com
  - url: 'https://github.com/logto-io/logto/security/advisories/GHSA-qp7j-c3q2-g739'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.00631
epssPercentile: 0.48901
ingestedAt: '2026-09-09T21:22:45.543Z'
---

## Overview

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's email subaddressing blocklist in packages/core/src/libraries/sign-in-experience/email-blocklist-policy.ts used the attacker-controlled domain from email input to construct subaddressingRegex when blockSubaddressing was enabled. The permissive emailRegEx accepted multiple at signs and regular expression metacharacters, and POST /api/experience/verification/verification-code could therefore cause catastrophic backtracking in subaddressingRegex.test(email). The resulting event-loop stall could make authentication, token issuance, SSO, and the administrative console unavailable. This issue is fixed in version 1.41.0.

## Remediation

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