Quick answers
- Is CVE-2026-54714 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54714 being exploited in the wild.
- How severe is CVE-2026-54714?
- Medium severity, with a CVSS score of 6.1, published 10 July 2026.
- Which products and versions are affected?
- Logto < 1.41.0.
- Is there a fix for CVE-2026-54714?
- A patch was published on 2026-06-12: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54714 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-54714?
- 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 reflected Cross-Site Scripting (XSS) vulnerability exists in @logto/core prior to version 1.41.0. The vulnerable component, `packages/core/src/saml-application/SamlApplication/utils.ts`, fails to perform HTML-attribute escaping when reflecting the `RelayState`, `SAMLResponse`, and `actionUrl` parameters into an auto-submitting HTML form. An attacker can exploit this by crafting a malicious SAML authentication request (via GET or POST to `/api/saml/:id/authn`) containing a payload in the `RelayState`. When a user completes the login flow, the injected script executes within the context of the Logto tenant origin. The fix, introduced in version 1.41.0, implements proper HTML escaping for these attributes and restricts the `actionUrl` to authorized web schemes.
Affected products
- logto-io logto < 1.41.0
Timeline
- 2026-06-12: patched: Fix committed to repository
- 2026-06-30: advisory: Release v1.41.0 published
- 2026-07-10: disclosed: CVE-2026-54714 published