Is CVE-2026-55789 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55789 being exploited in the wild.

How severe is CVE-2026-55789?

High severity, with a CVSS score of 8.5, published 10 July 2026.

Is there a fix for CVE-2026-55789?

A patch was published on 2026-06-30: Fix merged and version 1.41.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55789 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-55789?

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.

CVE-2026-55789: Logto XML injection in SAML IdP profile attributes

CVE-2026-55789 · Severity: high · CVSS 8.5 · Published 2026-07-10

Logto is an open-source authentication platform used to manage user identities for applications. A security flaw in its SAML identity provider component allowed users to inject malicious code into their own profile information, such as their name or email. Because this information was not properly cleaned before being included in security tokens, a regular user could trick the system into granting them administrative privileges or other unauthorized roles in connected applications.

Technologies: Logto. Vendors: Logto.

Quick answers

Is CVE-2026-55789 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55789 being exploited in the wild.
How severe is CVE-2026-55789?: High severity, with a CVSS score of 8.5, published 10 July 2026.
Which products and versions are affected?: Logto < 1.41.0.
Is there a fix for CVE-2026-55789?: A patch was published on 2026-06-30: Fix merged and version 1.41.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55789 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-55789?: 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

An XML injection vulnerability exists in Logto's self-hosted SAML application IdP due to the use of an outdated version of the 'samlify' library (2.10.0). The application performed string substitution of user-controlled profile attributes (like name and email) into element-text placeholders within a SAML XML template without proper escaping. An authenticated attacker could provide a crafted profile attribute containing XML markup to close existing tags and inject new ones, such as arbitrary roles or group memberships. Because these injected elements are included within the signed portion of the SAML assertion, relying Service Providers (SPs) would accept the forged attributes as authentic, leading to cross-application privilege escalation. The issue is resolved in version 1.41.0 by upgrading samlify to version 2.13.0 or higher.

Affected products

logto-io Logto < 1.41.0

Timeline

2026-05-29: other: Vulnerability verified on live master branch
2026-06-30: patched: Fix merged and version 1.41.0 released
2026-07-01: advisory: GitHub Security Advisory published
2026-07-10: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.