CVE-2026-63188

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (46th 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

Also known asEUVD-2026-62867 (ENISA EUVD) · GHSA-rxjr-6c9q-h67x (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 0.3.9, the Logto Tunnel npm package enabled createStaticFileProxy from packages/tunnel/src/commands/tunnel/index.ts and passed request.url from static asset requests through packages/tunnel/src/commands/tunnel/utils.ts using path.join(staticPath, request.url) and then fs.open(requestPath, "r") without URL normalization or a containment check. When --experience-path was enabled and the tunnel port was reachable, an unauthenticated requester could send a path containing ../ to createStaticFileProxy and read files outside the configured static directory that were readable by the logto-tunnel process. The service used server.listen(port), which could expose the tunnel to other hosts depending on the platform and deployment. This issue is fixed in version 0.3.9.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
46th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit Patch Available

commit 568681595553 (logto-io/logto)

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

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

fix(tunnel): prevent static path traversal

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

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

logto-tunnel serves files outside --experience-path via path traversal · Advisory · logto-io/logto · GitHub

https://github.com/logto-io/logto/security/advisories/GHSA-rxjr-6c9q-h67x

Vendor Advisories for CVE-2026-63188(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@logto/tunnel @ 0.3.9 (fixes <= 0.3.8)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@logto/tunnel—
  • every version up to 0.3.9: fixed in 0.3.9
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 151 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 18:26 UTCOSV refresh
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  3. 2026-11-21 01:37 UTCEchelonGraph re-scored
  4. 2026-11-21 01:37 UTCGHSA enrichmentGHSA-rxjr-6c9q-h67x · GitHub severity HIGH
  5. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  6. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  7. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  8. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  9. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  10. 2026-11-15 17:01 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  12. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-11-13 09:35 UTCEchelonGraph re-scored
  14. 2026-11-13 09:35 UTCGHSA enrichmentGHSA-rxjr-6c9q-h67x · GitHub severity HIGH
  15. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  16. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  17. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  18. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  19. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  20. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  21. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  22. 2026-11-05 17:33 UTCEchelonGraph re-scored
  23. 2026-11-05 17:33 UTCGHSA enrichmentGHSA-rxjr-6c9q-h67x · GitHub severity HIGH
  24. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  25. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
Show 75 more
  1. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  4. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-rxjr-6c9q-h67x · GitHub severity HIGH
  5. 2026-11-01 07:41 UTCEchelonGraph re-scored
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-10-29 01:31 UTCEchelonGraph re-scored
  10. 2026-10-28 22:25 UTCOSV refresh
  11. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  15. 2026-10-25 14:13 UTCEchelonGraph re-scored
  16. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-21 04:15 UTCEchelonGraph re-scored
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-18 03:23 UTCEchelonGraph re-scored
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  26. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  27. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  28. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  29. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-13 12:03 UTCEchelonGraph re-scored
  31. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-12 15:49 UTCEchelonGraph re-scored
  33. 2026-10-11 19:33 UTCEchelonGraph re-scored
  34. 2026-10-11 16:48 UTCEchelonGraph re-scored
  35. 2026-10-11 14:10 UTCEchelonGraph re-scored
  36. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-10-08 07:29 UTCEchelonGraph re-scored
  41. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-10-06 21:20 UTCEchelonGraph re-scored
  43. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  44. 2026-10-06 07:55 UTCEchelonGraph re-scored
  45. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-10-05 10:05 UTCEchelonGraph re-scored
  47. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-10-03 16:54 UTCEchelonGraph re-scored
  49. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  50. 2026-10-03 01:37 UTCEchelonGraph re-scored
  51. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-10-01 22:45 UTCEchelonGraph re-scored
  53. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  54. 2026-09-30 21:19 UTCEchelonGraph re-scored
  55. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  56. 2026-09-30 08:38 UTCEchelonGraph re-scored
  57. 2026-09-28 21:41 UTCEchelonGraph re-scored
  58. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  59. 2026-09-27 18:40 UTCEchelonGraph re-scored
  60. 2026-09-27 05:59 UTCEchelonGraph re-scored
  61. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  62. 2026-09-25 00:48 UTCEchelonGraph re-scored
  63. 2026-09-23 21:19 UTCEchelonGraph re-scored
  64. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  65. 2026-09-22 19:57 UTCEchelonGraph re-scored
  66. 2026-09-22 07:14 UTCEchelonGraph re-scored
  67. 2026-09-21 05:52 UTCEchelonGraph re-scored
  68. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  69. 2026-09-20 03:02 UTCEchelonGraph re-scored
  70. 2026-09-19 01:38 UTCEchelonGraph re-scored
  71. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  72. 2026-09-18 00:12 UTCEchelonGraph re-scored
  73. 2026-09-16 22:45 UTCEchelonGraph re-scored
  74. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  75. 2026-09-16 09:51 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-63188?
CVE-2026-63188 is a high-severity vulnerability; its CVE record was published on August 19, 2026. Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 0.3.9, the Logto Tunnel npm package enabled createStaticFileProxy from packages/tunnel/src/commands/tunnel/index.ts and passed request.url from static asset requests through…
When was the CVE record for CVE-2026-63188 published?
The CVE record for CVE-2026-63188 was published on August 19, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-63188 actively exploited?
CVE-2026-63188 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63188?
CVE-2026-63188 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63188?
A fix for CVE-2026-63188 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63188 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63188

Explore →

Is Your Infrastructure Affected by CVE-2026-63188?

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