openhole-server vulnerable to path traversal via URL-decoded request path

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

Source published

28 Jul 2026 22:20:51 UTC

Source modified

18 Aug 2026 15:10:46 UTC

Observed here

24 Oct 2026 13:19:41 UTC

Source terms

GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Publisher rating · HIGH