CVE-2026-63188
Unauthenticated path-traversal in Logto Tunnel allows reading files outside configured static directory.
Is CVE-2026-63188 being exploited?
Not confirmed. CVE-2026-63188 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-63188?
CVE-2026-63188 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63188?
Yes. A fix has been recorded for CVE-2026-63188. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63188 affect?
CVE-2026-63188 affects logto-tunnel npm package < 0.3.9, Applications using Logto with --experience-path, Deployments exposing the tunnel port. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63188?
Upgrade to logto-tunnel v0.3.9 and restrict/block tunnel network access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated ../ path traversal in static file handling lets attackers read any file the process can access; tunnel may be network-exposed.
Immediate action required
- affected< 0.3.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.