CVE-2026-55789

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's self-hosted SAML application IdP built the signed SAML response and assertion by string-substituting user-controlled profile attributes such as name, email, and custom attribute-mapping values into element-text placeholders of a SAML XML template using samlify 2.10.0, which left those placeholders unescaped. An authenticated low-privilege user could place XML markup in a profile attribute so Logto signed a forged SAML attribute, such as an arbitrary role, allowing privilege escalation at relying Service Providers that authorize on SAML attributes. This issue is fixed in version 1.41.0.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
—
EPSS
22.0%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

SAML IdP injects user-controlled profile attributes raw into signed assertions, allowing privilege escalation at relying Service Providers · Advisory · logto-io/logto · GitHub

https://github.com/logto-io/logto/security/advisories/GHSA-vfpw-vq44-4p63
github_release Patch Available

v1.41.0

Patch available: logto-io/logto v1.41.0

https://github.com/logto-io/logto/releases/tag/v1.41.0
github_pr Patch Available

fix(core): upgrade samlify to ^2.13.0

Patch available: logto-io/logto v1.41.0 (PR #9107 merged 2026-06-30)

https://github.com/logto-io/logto/pull/9107
github_commit Patch Available

commit 9097054860f0 (logto-io/logto)

Patch available: logto-io/logto v1.41.0 (contains commit 9097054860f0)

https://github.com/logto-io/logto/commit/9097054860f0d638d90778d3dcde2ba050b844b6

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-10 20:04 UTCEG score recompute
  18. 2026-07-10 20:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55789?
CVE-2026-55789 is a high vulnerability published on July 10, 2026. Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's self-hosted SAML application IdP built the signed SAML response and assertion by string-substituting user-controlled profile attributes such as name, email, and custom attribute-mapping values into…
When was CVE-2026-55789 disclosed?
CVE-2026-55789 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55789 actively exploited?
CVE-2026-55789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55789?
CVE-2026-55789 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-55789?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55789, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55789

Explore →

Is Your Infrastructure Affected by CVE-2026-55789?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs