{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55377 exists.","fix":"No fix has been published for CVE-2026-55377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55377 is a high-severity authentication bypass vulnerability in logto-io logto, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55377 and fix it if it is affected.\n\nWhat it is: CVE-2026-55377 is a high-severity authentication bypass vulnerability in logto-io logto, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55377 exists.\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-55377/ (Markdown: https://insights.sbomify.com/CVE-2026-55377/index.md)","id":"CVE-2026-55377","markdown":"https://insights.sbomify.com/CVE-2026-55377/index.md","name":"CVE-2026-55377","record":{"aliases":["GHSA-q4h3-38gc-4p4j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Logto auth infrastructure","requires_auth":"low_privilege","summary":"Attackers can bypass MFA step-up checks in Logto's Account Center to manage MFA factors without proving possession of existing credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Logto: Account Center MFA management step-up bypass via WebAuthn registration verification","id":"CVE-2026-55377","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":"JS Recon: Command injection in PR Branch Checker workflow via untrusted pull request context values","id":"CVE-2026-55378"},"packages":[],"prev":{"headline":"heym Python Tool Sandbox Escape","id":"CVE-2026-55376"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["logto-io"]},"summary":"Attackers can bypass MFA step-up checks in Logto's Account Center to manage MFA factors without proving possession of existing credentials.","url":"https://insights.sbomify.com/CVE-2026-55377/"}