Quick answers
- Is CVE-2026-15614 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15614 being exploited in the wild.
- How severe is CVE-2026-15614?
- Informational severity, with a CVSS score of 0, published 23 July 2026.
- Which products and versions are affected?
- Logto 1.21.0 to 1.37.1.
- Is there a fix for CVE-2026-15614?
- 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-15614 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-15614?
- 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
A session management vulnerability exists in Logto's SAML implementation, specifically within the single sign-on verification helpers. The application fails to properly delete or invalidate session identifiers for IdP-initiated SAML flows upon completion or logout. This root cause allows for session replay attacks, where a valid SAML session token can be reused by an unauthorized party within its original validity window. The issue is located in the core package's single-sign-on.ts library. Affected versions range from 1.21.0 to 1.37.1.
Affected products
- Logto Logto 1.21.0 to 1.37.1
Timeline
- 2026-07-23: disclosed: CVE published by NVD/CERT/CC