CVE-2026-54714

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
Trending — 3 sources updated this week
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: 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/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.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
16.6%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

XSS via unescaped RelayState in SAML auto-submit form · Advisory · logto-io/logto · GitHub

https://github.com/logto-io/logto/security/advisories/GHSA-cpm5-w86q-w85f
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): escape HTML attribute values in SAML auto-submit form

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

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

commit 209fa0a5cbe8 (logto-io/logto)

Patch available: logto-io/logto v1.41.0 (contains commit 209fa0a5cbe8)

https://github.com/logto-io/logto/commit/209fa0a5cbe8522f9cf31873239dc6424099bb5e

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-16 01:46 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 00:39 UTCEG score recompute
  7. 2026-07-13 23:26 UTCEG score recompute
  8. 2026-07-13 22:31 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 22:18 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 21:11 UTCEG score recompute
  14. 2026-07-10 20:04 UTCEG score recompute
  15. 2026-07-10 20:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54714?
CVE-2026-54714 is a medium 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/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…
When was CVE-2026-54714 disclosed?
CVE-2026-54714 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-54714 actively exploited?
CVE-2026-54714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54714?
CVE-2026-54714 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-54714?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54714, 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-54714

Explore →

Is Your Infrastructure Affected by CVE-2026-54714?

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

Start Free Scan →Browse All CVEs