6.1
MEDIUM CVSS 3.1
CVE-2026-54714
Logto: XSS via unescaped RelayState in SAML auto-submit form
Description

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, @logto/core reflected the SAML RelayState, SAMLResponse, and actionUrl into a Logto-origin auto-submit HTML form in packages/core/src/saml-application/SamlApplication/utils.ts without HTML-attribute escaping. A SAML application flow with a crafted RelayState from GET or POST /api/saml/:id/authn could inject script that runs on the Logto tenant origin after the user completes login. This issue is fixed in version 1.41.0.

INFO

Published Date :

July 10, 2026, 8:16 p.m.

Last Modified :

July 10, 2026, 8:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-54714 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update Logto to version 1.41.0 or later to fix the SAML RelayState reflection vulnerability.
  • Update Logto to version 1.41.0 or later.
  • Ensure SAML RelayState values are properly escaped.
  • Review application SAML integration configurations.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-54714 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-54714 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-54714 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-54714 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 10, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'logto-io', 'product': 'logto', 'versions': [{'status': 'affected', 'version': '< 1.41.0'}]}]
    Added Description Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, @logto/core reflected the SAML RelayState, SAMLResponse, and actionUrl into a Logto-origin auto-submit HTML form in packages/core/src/saml-application/SamlApplication/utils.ts without HTML-attribute escaping. A SAML application flow with a crafted RelayState from GET or POST /api/saml/:id/authn could inject script that runs on the Logto tenant origin after the user completes login. This issue is fixed in version 1.41.0.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
    Added CWE CWE-79
    Added Reference https://github.com/logto-io/logto/commit/209fa0a5cbe8522f9cf31873239dc6424099bb5e
    Added Reference https://github.com/logto-io/logto/pull/9008
    Added Reference https://github.com/logto-io/logto/releases/tag/v1.41.0
    Added Reference https://github.com/logto-io/logto/security/advisories/GHSA-cpm5-w86q-w85f
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.