CVE-2026-63203

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-86223 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. From 1.31.0 until 1.42.0, the Account API handlers in packages/core/src/routes/account/third-party-tokens.ts allow a caller holding a same-user access token with only the openid scope to retrieve stored social or enterprise SSO provider access tokens through GET /api/my-account/identities/{target}/access-token or GET /api/my-account/sso-identities/{connectorId}/access-token. The handlers authenticate the user but do not require the identities scope that protects neighboring identity-detail operations, bypassing the intended Account API consent boundary. Exploitation requires federated token-set storage to be enabled and the affected user to have authenticated through a supported connector. A low-trust application can use the disclosed provider token against upstream APIs within that token's granted scopes. This issue is fixed in version 1.42.0.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 24, 2026
Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

v1.42.0

Patch available: logto-io/logto v1.42.0

https://github.com/logto-io/logto/releases/tag/v1.42.0
GitHub commit Patch Available

commit b560d17a4da4 (logto-io/logto)

Patch available: logto-io/logto v1.42.0 (contains commit b560d17a4da4)

https://github.com/logto-io/logto/commit/b560d17a4da4c25da95e3c73af4485d18ab7c224
GitHub pull request Patch Available

fix(core): require the identities scope for Account API third-party token endpoints

Patch available: logto-io/logto v1.42.0 (PR #9116 merged 2026-07-02)

https://github.com/logto-io/logto/pull/9116
GitHub advisoryMentions a patch (unverified)

Account API can disclose stored third-party provider tokens without the identities scope · Advisory · logto-io/logto · GitHub

https://github.com/logto-io/logto/security/advisories/GHSA-6g9q-qrx7-3jxf

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-28 06:04 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-25 14:13 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-20 18:52 UTCEG score recompute
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-18 03:23 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-13 12:03 UTCEG score recompute
Show 40 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-12 15:49 UTCEG score recompute
  3. 2026-10-11 19:33 UTCEG score recompute
  4. 2026-10-11 16:48 UTCEG score recompute
  5. 2026-10-11 14:10 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-10 21:53 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-09 23:40 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-08 23:38 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-08 01:33 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-06 16:22 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-05 18:08 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-05 07:05 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-03 21:57 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-02 23:53 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-02 01:47 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-09-30 16:37 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-09-29 18:15 UTCEG score recompute
  30. 2026-09-29 07:11 UTCEG score recompute
  31. 2026-09-28 20:05 UTCEG score recompute
  32. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-27 21:54 UTCEG score recompute
  34. 2026-09-26 23:48 UTCEG score recompute
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-09-26 01:41 UTCEG score recompute
  37. 2026-09-24 16:35 UTCEG score recompute
  38. 2026-09-24 15:52 UTCEG score recompute
  39. 2026-09-24 15:32 UTCEG score recomputeFirst assessed: 7.6 HIGH
  40. 2026-09-24 15:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63203?
CVE-2026-63203 is a high-severity vulnerability; its CVE record was published on September 24, 2026. Logto is the modern, open-source auth infrastructure for SaaS and AI apps. From 1.31.0 until 1.42.0, the Account API handlers in packages/core/src/routes/account/third-party-tokens.ts allow a caller holding a same-user access token with only the openid scope to retrieve stored social or enterprise…
When was the CVE record for CVE-2026-63203 published?
The CVE record for CVE-2026-63203 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-63203 actively exploited?
CVE-2026-63203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63203?
CVE-2026-63203 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63203?
A fix for CVE-2026-63203 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63203?

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

Book a Demo →Browse All CVEs