CVE-2026-15617 Logto vulnerability
Logto performs principal lookup without normalizing email and identifier strings, enabling principal collision and unauthorized account access via case- or Unicode-different identities.
Quick answer
Logto should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- <= 1.37.1
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-15617 affects Logto and involves security-control failure. Successful exploitation may affect the confidentiality, integrity, or availability of the affected workflow. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. No confirmed fixed version is recorded for CVE-2026-15617; follow the linked vendor advisory, apply its mitigation, and update Logto as soon as a supported patched release is available.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Logto.
- Compare the installed version with the recorded affected range: <= 1.37.1.
- No confirmed fixed version is recorded for CVE-2026-15617; follow the linked vendor advisory, apply its mitigation, and update Logto as soon as a supported patched release is available.
- Until patched, reduce public exposure, disable the affected workflow where practical, and allow access only from trusted users and systems.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Logto; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-15617 in place.
- Use a safe regression test to confirm the affected security-control failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Trusted references
FAQ
What is affected by CVE-2026-15617?
Logto versions listed as affected should be reviewed: <= 1.37.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.