Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's existing TOTP verification accepted a successfully used TOTP code again while the code remained inside the RFC 6238 acceptance window because the verifier used otplib's stateless check with window = 1 and did not persist or compare the accepted TOTP time-step counter. An attacker who has the victim's first factor and captures a live TOTP value can replay that value to satisfy MFA during the same acceptance window. This issue is fixed in version 1.41.0.
CVE-2026-55370
MEDIUMPre-NVD 6.46.4
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 6.4Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(low)
- EPSS
- —
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available
TOTP code can be replayed within the RFC 6238 acceptance window · Advisory · logto-io/logto · GitHub
https://github.com/logto-io/logto/security/advisories/GHSA-6wj7-c66m-6c82github_release Patch Available
v1.41.0
Patch available: logto-io/logto v1.41.0
https://github.com/logto-io/logto/releases/tag/v1.41.0github_pr Patch Available
fix: prevent TOTP replay
Patch available: logto-io/logto v1.41.0 (PR #9109 merged 2026-06-30)
https://github.com/logto-io/logto/pull/9109github_commit Patch Available
commit 9118867f6cba (logto-io/logto)
Patch available: logto-io/logto v1.41.0 (contains commit 9118867f6cba)
https://github.com/logto-io/logto/commit/9118867f6cbadc7291cf913beb4fede91ed5d374Frequently asked(4)
What is CVE-2026-55370?
CVE-2026-55370 is a medium vulnerability published on July 10, 2026. Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's existing TOTP verification accepted a successfully used TOTP code again while the code remained inside the RFC 6238 acceptance window because the verifier used otplib's stateless check with window =…
When was CVE-2026-55370 disclosed?
CVE-2026-55370 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-55370?
CVE-2026-55370 has a CVSS v3 base score of 6.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55370, 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-55370
Is Your Infrastructure Affected by CVE-2026-55370?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.