Vulnerability-Lookup

GHSA-RXJR-6C9Q-H67X

Vulnerability from github – Published: 2026-08-19 20:24 – Updated: 2026-08-19 20:24

Summary

logto-tunnel serves files outside --experience-path via path traversal

Details

Summary

@logto/tunnel serves custom sign-in experience files from the --experience-path directory. When the tunnel service is reachable, a requester can use ../ path segments in a static asset request to read files outside that directory that the CLI process can read.

Details

The tunnel command accepts --experience-path as the local folder path for custom sign-in experience assets. packages/tunnel/src/commands/tunnel/index.ts enables createStaticFileProxy(path) when that option is set and sends non-Logto, non---experience-uri requests to that static proxy. The server is started with server.listen(port).

packages/tunnel/src/commands/tunnel/utils.ts builds the filesystem path as path.join(staticPath, fallBackToIndex ? index : request.url). For file asset paths, request.url is used directly. A request URL such as /../secret.txt resolves outside staticPath and is then opened with fs.open(requestPath, 'r'). There is no URL normalization and no containment check that the resolved path remains under the configured static directory before the file is read and returned.

The proof boundary is the packaged CLI end-to-end run. The filesystem read primitive was validated with equivalent Node HTTP handling for the affected code path, including that Node preserves /../secret.txt in request.url and that bare server.listen(port) binds to all interfaces on this platform.

PoC

Create a custom UI directory at /tmp/logto-ui/static with /tmp/logto-ui/static/index.html.
Create a sibling file outside the static root, for example /tmp/logto-ui/secret.txt.
Start the tunnel with logto-tunnel --endpoint https://<tenant-id>.logto.app --port 9000 --experience-path /tmp/logto-ui/static.
Request http://<host>:9000/../secret.txt.
The response body contains the contents of /tmp/logto-ui/secret.txt.

Impact

The observed result is arbitrary file read outside the configured custom UI static directory. If the tunnel port is reachable from another host, an unauthenticated network peer can read local files readable by the logto-tunnel process, including development secrets or credentials stored near the custom UI project.

Severity

8.7 (High)


                  
                    CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.3.8"
      },
      "package": {
        "ecosystem": "npm",
        "name": "@logto/tunnel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.3.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-63188"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-19T20:24:06Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Summary\n\n`@logto/tunnel` serves custom sign-in experience files from the `--experience-path` directory. When the tunnel service is reachable, a requester can use `../` path segments in a static asset request to read files outside that directory that the CLI process can read.\n\n### Details\n\nThe tunnel command accepts `--experience-path` as the local folder path for custom sign-in experience assets. `packages/tunnel/src/commands/tunnel/index.ts` enables `createStaticFileProxy(path)` when that option is set and sends non-Logto, non-`--experience-uri` requests to that static proxy. The server is started with `server.listen(port)`.\n\n`packages/tunnel/src/commands/tunnel/utils.ts` builds the filesystem path as `path.join(staticPath, fallBackToIndex ? index : request.url)`. For file asset paths, `request.url` is used directly. A request URL such as `/../secret.txt` resolves outside `staticPath` and is then opened with `fs.open(requestPath, \u0027r\u0027)`. There is no URL normalization and no containment check that the resolved path remains under the configured static directory before the file is read and returned.\n\nThe proof boundary is the packaged CLI end-to-end run. The filesystem read primitive was validated with equivalent Node HTTP handling for the affected code path, including that Node preserves `/../secret.txt` in `request.url` and that bare `server.listen(port)` binds to all interfaces on this platform.\n\n### PoC\n\n1. Create a custom UI directory at `/tmp/logto-ui/static` with `/tmp/logto-ui/static/index.html`.\n2. Create a sibling file outside the static root, for example `/tmp/logto-ui/secret.txt`.\n3. Start the tunnel with `logto-tunnel --endpoint https://\u003ctenant-id\u003e.logto.app --port 9000 --experience-path /tmp/logto-ui/static`.\n4. Request `http://\u003chost\u003e:9000/../secret.txt`.\n5. The response body contains the contents of `/tmp/logto-ui/secret.txt`.\n\n### Impact\n\nThe observed result is arbitrary file read outside the configured custom UI static directory. If the tunnel port is reachable from another host, an unauthenticated network peer can read local files readable by the `logto-tunnel` process, including development secrets or credentials stored near the custom UI project.",
  "id": "GHSA-rxjr-6c9q-h67x",
  "modified": "2026-08-19T20:24:06Z",
  "published": "2026-08-19T20:24:06Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/logto-io/logto/security/advisories/GHSA-rxjr-6c9q-h67x"
    },
    {
      "type": "WEB",
      "url": "https://github.com/logto-io/logto/pull/9113"
    },
    {
      "type": "WEB",
      "url": "https://github.com/logto-io/logto/commit/5686815955534f803d3d50738259efd0f741e62c"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/logto-io/logto"
    },
    {
      "type": "WEB",
      "url": "https://github.com/logto-io/logto/releases/tag/@logto/tunnel@0.3.9"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "logto-tunnel serves files outside --experience-path via path traversal"
}

CVE-2026-63188 (GCVE-0-2026-63188)

Vulnerability from cvelistv5 – Published: 2026-08-19 19:47 – Updated: 2026-08-19 19:47

Title

logto-tunnel serves files outside --experience-path via path traversal

Summary

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.

Severity

8.7 (High)


                        
                          CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CWE

CWE-22 - Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Assigner

GitHub_M mitre root

References

4 references

URL	Tags
https://github.com/logto-io/logto/security/adviso…	x_refsource_CONFIRM
https://github.com/logto-io/logto/pull/9113	x_refsource_MISC
https://github.com/logto-io/logto/commit/56868159…	x_refsource_MISC
https://github.com/logto-io/logto/releases/tag/@l…	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
logto-io	logto	Affected: < 0.3.9

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "logto",
          "vendor": "logto-io",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.3.9"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.7,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-22",
              "description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-19T19:47:05.155Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/logto-io/logto/security/advisories/GHSA-rxjr-6c9q-h67x",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/logto-io/logto/security/advisories/GHSA-rxjr-6c9q-h67x"
        },
        {
          "name": "https://github.com/logto-io/logto/pull/9113",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/logto-io/logto/pull/9113"
        },
        {
          "name": "https://github.com/logto-io/logto/commit/5686815955534f803d3d50738259efd0f741e62c",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/logto-io/logto/commit/5686815955534f803d3d50738259efd0f741e62c"
        },
        {
          "name": "https://github.com/logto-io/logto/releases/tag/@logto/tunnel@0.3.9",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/logto-io/logto/releases/tag/@logto/tunnel@0.3.9"
        }
      ],
      "source": {
        "advisory": "GHSA-rxjr-6c9q-h67x",
        "discovery": "UNKNOWN"
      },
      "title": "logto-tunnel serves files outside --experience-path via path traversal"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-63188",
    "datePublished": "2026-08-19T19:47:05.155Z",
    "dateReserved": "2026-07-15T22:13:00.721Z",
    "dateUpdated": "2026-08-19T19:47:05.155Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.

Action not permitted

GHSA-RXJR-6C9Q-H67X

Summary

Details

PoC

Impact

CVE-2026-63188 (GCVE-0-2026-63188)

Tags

Sightings

Nomenclature