CVE-2026-62317

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 21, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.41.0

Patch available: logto-io/logto v1.41.0

https://github.com/logto-io/logto/releases/tag/v1.41.0
github_commit Patch Available

commit 021381237511 (logto-io/logto)

Patch available: logto-io/logto v1.41.0 (contains commit 021381237511)

https://github.com/logto-io/logto/commit/021381237511bc0d42f81d65df8b036b01f40547
github_pr Patch Available

fix(core): avoid regex in email subaddressing blocklist check

Patch available: logto-io/logto v1.41.0 (PR #9106 merged 2026-06-30)

https://github.com/logto-io/logto/pull/9106
github Patch Available

ReDoS via unescaped user input in email subaddressing regex (blockSubaddressing) · Advisory · logto-io/logto · GitHub

https://github.com/logto-io/logto/security/advisories/GHSA-qp7j-c3q2-g739

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 15:51 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 17:01 UTCEG score recompute
  4. 2026-08-23 06:38 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 07:48 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 20:23 UTCEG score recompute
  9. 2026-08-21 19:20 UTCEG score recompute
  10. 2026-08-21 06:33 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 20:20 UTCEG score recompute
  13. 2026-08-19 19:43 UTCEG score recompute
  14. 2026-08-19 19:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62317?
CVE-2026-62317 is a high vulnerability published on August 19, 2026. 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…
When was CVE-2026-62317 disclosed?
CVE-2026-62317 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62317 actively exploited?
CVE-2026-62317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62317?
CVE-2026-62317 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-62317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62317, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62317

Explore →

Is Your Infrastructure Affected by CVE-2026-62317?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs