Quick answers
- Is CVE-2026-15612 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15612 being exploited in the wild.
- How severe is CVE-2026-15612?
- Informational severity, published 23 July 2026.
- Which products and versions are affected?
- Logto 1.10.1 to 1.37.1.
- Is there a fix for CVE-2026-15612?
- 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-15612 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15612?
- 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 vulnerability exists in Logto's OIDC Connector where the system fails to enforce nonce validation if the 'nonce' claim is missing from the ID token. This occurs within the OidcConnector utility logic. By omitting the nonce claim, an attacker can bypass the security check intended to ensure that an authentication response corresponds to a specific original request. This flaw facilitates replay attacks and weakens the binding between the user's session and the authentication event. The issue affects versions 1.10.1 through 1.37.1.
Affected products
- Logto Logto 1.10.1 to 1.37.1
Timeline
- 2026-07-23: disclosed
- 2026-07-23: advisory