CVE-2026-15614 Logto vulnerability
Logto silently fails to delete IdP-initiated SAML sessions, enabling session replay and reuse within the session’s validity window.
Browse SAML security risksQuick 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-15614 affects Logto and involves cryptographic validation failure. A validation failure may make the application trust an invalid peer, signature, token, or cryptographic result. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. No confirmed fixed version is recorded for CVE-2026-15614; 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-15614; follow the linked vendor advisory, apply its mitigation, and update Logto as soon as a supported patched release is available.
- Until patched, disable the affected integration or require an independently verified trusted endpoint and certificate or signature policy.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Logto; remove access that is not required.
- Review TLS, authentication, signature, and connection logs for untrusted peers, certificate errors, downgrade behavior, or unexpected trust decisions.
- 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-15614 in place.
- Use a safe regression test to confirm the affected cryptographic validation 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.
Related categories
Related security risks
More published guidance from the same primary category.
CVE-2026-15615 Logto vulnerability
Updated July 24, 2026
criticalSAML Single Sign On <= 5.4.4 - Unauthenticated Authentication Bypass via SAMLResponse Parameter
Updated July 24, 2026
mediumSAML Single Sign On <= 5.4.3 - Unauthenticated Authentication Bypass via 'SAMLResponse' Parameter Signature Algorithm Confusion
Updated July 15, 2026
Trusted references
FAQ
What is affected by CVE-2026-15614?
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.