Logto silently fails to delete IdP-initiated SAML sessions, enabling session replay and reuse within the session’s validity window.
CVE-2026-15614
This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 27, 2026
Advisory Details (1)
Auto-updated Jul 27, 2026logto/packages/core/src/libraries/verification-helpers/single-sign-on.ts at ea3ede35028dfd0bbb6d7b239623ce0e7f6cdff8 · logto-io/logto · GitHub
https://github.com/logto-io/logto/blob/ea3ede35028dfd0bbb6d7b239623ce0e7f6cdff8/packages/core/src/libraries/verification-helpers/single-sign-on.ts#L81-L99Vendor Advisories for CVE-2026-15614(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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.
- 2026-07-27 16:17 UTCEG score recompute▲ 7.50
- 2026-07-27 16:17 UTCGHSA enrichment
- 2026-07-27 16:16 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:07 UTCEG score recompute
- 2026-07-26 03:07 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 16:20 UTCNVD update
- 2026-07-23 16:17 UTCEG score recompute
- 2026-07-23 16:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-294
- CVE-2021-22640NVD 7.5EG 9.8CRITICAL
- CVE-2022-29334EG 9.8CRITICAL
- CVE-2022-22806EG 9.8EPSS p96CRITICAL
- CVE-2020-35551EG 9.8CRITICAL
- CVE-2018-19025EG 9.8CRITICAL
- CVE-2018-17932EG 9.8CRITICAL
- CVE-2019-18226EG 9.8CRITICAL
- CVE-2018-7790EG 9.8CRITICAL
- CVE-2017-3191EG 9.8EPSS p99CRITICAL
- CVE-2017-6034EG 9.8EPSS p92CRITICAL
Frequently asked(5)
What is CVE-2026-15614?
When was CVE-2026-15614 disclosed?
Is CVE-2026-15614 actively exploited?
What is the CVSS score of CVE-2026-15614?
How do I remediate CVE-2026-15614?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15614
Is Your Infrastructure Affected by CVE-2026-15614?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.