{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-55370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-55370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55370 is a medium-severity authentication bypass vulnerability in logto-io logto, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-55370 and fix it if it is affected.\n\nWhat it is: CVE-2026-55370 is a medium-severity authentication bypass vulnerability in logto-io logto, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-55370 in the wild and no public exploit code.\n\nAffected product: logto-io logto. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55370/ (Markdown: https://insights.sbomify.com/CVE-2026-55370/index.md)","id":"CVE-2026-55370","markdown":"https://insights.sbomify.com/CVE-2026-55370/index.md","name":"CVE-2026-55370","record":{"aliases":["GHSA-6wj7-c66m-6c82"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Logto authentication server","requires_auth":"low_privilege","summary":"Attackers can replay captured TOTP codes within the validity window to bypass MFA and take over accounts if they possess the first factor.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Logto: TOTP code can be replayed within the RFC 6238 validity window (one-time use violation)","id":"CVE-2026-55370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenEXR: OpenEXRCore exr_attr_set_bytes() accepts NULL type_hint with positive hint_length","id":"CVE-2026-55371"},"packages":[],"prev":{"headline":"Waline login accepts a non-string email as a match-all MongoDB query","id":"CVE-2026-55369"},"products":["logto"],"published":"2026-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["logto-io"]},"summary":"Attackers can replay captured TOTP codes within the validity window to bypass MFA and take over accounts if they possess the first factor.","url":"https://insights.sbomify.com/CVE-2026-55370/"}