EUVD-2026-342366

fkie_cve-2026-54650

openhole exposes localhost to the internet in one command. In 0.1.1 and earlier, openhole-server in internal/server/public_proxy.go forwarded r.URL.Path instead of preserving the original request target with r.URL.EscapedPath(), allowing percent encoded dot segments %2e and separators %2f to reach tunneled local services as ../ and / for path traversal. This issue is fixed in version 0.1.2.

GHSA-fh2f-xfxc-q9cc — openhole-server vulnerable to path traversal via URL-decoded request path

Affected: Go: github.com/bablilayoub/openhole

## Summary

openhole-server forwarded the URL-decoded request path (`r.URL.Path`) to tunnel clients instead of the original request-target. Percent-encoded dot-segments (`%2e`) and separators (`%2f`) were decoded to `../` and `/` before reaching the local service.

Go's ServeMux rejects literal `../` paths, but percent-encoded traversal sequences bypassed this and were delivered to backends as working path traversal.

## Impact

An unauthenticated remote attacker could read files outside the published web root on tunneled local services that resolve paths without canonicalization.

Example: - `/%2e%2e/secret.txt` → file outside web root - `/%2e%2e/%2e%2e/etc/passwd` → sensitive files

Encoded slashes (`/a%2fb`) could also bypass path-based access controls.

## Fix

v0.1.2 forwards `r.URL.EscapedPath()` on the server and preserves the request-target on the CLI client.

Users should upgrade both openhole-server and the openhole CLI to v0.1.2 or later.

Most recent entries from all

EUVD-2026-342366

fkie_cve-2026-54650

GHSA-fh2f-xfxc-q9cc — openhole-server vulnerable to path traversal via URL-decoded request path