logto-io logto up to 1.40.x SamlApplication utils.ts RelayState/SAMLResponse/actionurl cross site scripting

Summaryinfo

A vulnerability was found in logto-io logto up to 1.40.x. It has been rated as problematic. This issue affects some unknown processing of the file packages/core/src/saml-application/SamlApplication/utils.ts of the component SamlApplication. Performing a manipulation of the argument RelayState/SAMLResponse/actionurl results in cross site scripting. This vulnerability is identified as CVE-2026-54714. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in logto-io logto up to 1.40.x. It has been classified as problematic. This affects an unknown function of the file packages/core/src/saml-application/SamlApplication/utils.ts of the component SamlApplication. The manipulation of the argument RelayState/SAMLResponse/actionurl with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-54714 since 06/16/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 1.41.0 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• logto-io

Name

• logto

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40

Website

• Product: https://github.com/logto-io/logto/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion