Quick answers
- Is CVE-2026-15616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15616 being exploited in the wild.
- How severe is CVE-2026-15616?
- Informational severity, with a CVSS score of 0, published 23 July 2026.
- Which products and versions are affected?
- Logto 1.19.0 to 1.37.1.
- Is there a fix for CVE-2026-15616?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15616 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-15616?
- Check whether you run Logto at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass vulnerability exists in Logto versions 1.19.0 through 1.37.1. The root cause is a failure in the 'experience-interaction' component to enforce locally configured Multi-Factor Authentication (MFA) policies when a user authenticates via a Single Sign-On (SSO) provider. An attacker with valid SSO credentials can successfully authenticate to the Logto instance without being prompted for the secondary verification factors that would otherwise be required for local accounts. This bypasses the intended security posture of the identity provider. The vulnerability is located in the core routing logic responsible for managing user interaction sessions during the authentication flow.
Affected products
- Logto Logto 1.19.0 to 1.37.1
Timeline
- 2026-07-23: advisory: NVD published CVE-2026-15616