How severe is GHSA-rxjr-6c9q-h67x?

No CVSS score has been assigned to GHSA-rxjr-6c9q-h67x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rxjr-6c9q-h67x?

GHSA-rxjr-6c9q-h67x affects the following packages: @logto/tunnel (npm). Ecosystems affected: npm.

How do I fix GHSA-rxjr-6c9q-h67x?

Update @logto/tunnel to 0.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rxjr-6c9q-h67x is resolved across your whole dependency graph.

How do I detect GHSA-rxjr-6c9q-h67x in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @logto/tunnel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rxjr-6c9q-h67x if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-rxjr-6c9q-h67x actively exploited in the wild?

No public exploit code has been indexed for GHSA-rxjr-6c9q-h67x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rxjr-6c9q-h67x?

GHSA-rxjr-6c9q-h67x has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rxjr-6c9q-h67x?

GHSA-rxjr-6c9q-h67x is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rxjr-6c9q-h67x published, and has it been updated?

GHSA-rxjr-6c9q-h67x was published on August 19, 2026 and was last updated on August 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-rxjr-6c9q-h67x — @logto/tunnel

Fix: logto-io/logto#9113

GHSA-rxjr-6c9q-h67x is a Path Traversal vulnerability in @logto/tunnel. A fix is available for @logto/tunnel — see the affected versions and patch details below.

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

Also known asCVE-2026-63188

Published

Aug 19, 2026

Updated

Aug 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rxjr-6c9q-h67x.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@logto/tunnelnpm

189downloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@logto/tunnel`	all versions	0.3.9`npm install @logto/tunnel@0.3.9`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @logto/tunnel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @logto/tunnel to 0.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rxjr-6c9q-h67x is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### 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 i

O3 Security · Impact-Aware SCA

Is GHSA-rxjr-6c9q-h67x in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works