CVE-2026-63188 logto-tunnel serves files outside --experience-path via path traversal
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
Description
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.
Upgrade path
2 packages: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| Logto @logto/tunnel(npm) | < 0.3.9; <= 0.3.8 | 0.3.9 | Fixed |
| logto-io logto | = < 0.3.9 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| logto-io logto | = < 0.3.9 | No fix listed |
| Logto @logto/tunnel(npm) | <= 0.3.8 | No fix listed |
| Logto @logto/tunnel(npm) | < 0.3.9 | 0.3.9 |
References
- https://github.com/logto-io/logto/security/advisories/GHSA-rxjr-6c9q-h67x vendor-advisory
- https://github.com/logto-io/logto/pull/9113 patch
- https://github.com/logto-io/logto/commit/5686815955534f803d3d50738259efd0f741e62c patch
- https://github.com/logto-io/logto/releases/tag/@logto/tunnel@0.3.9
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com
- github.com product
- ENISA EUVD EUVD-2026-62867 third-party-advisory