github.com/bablilayoub/openhole
Affected
- introduced
0, fixed0.1.2(semver)
Fixed versions
0.1.2
Fix
- Fixed version
0.1.2go get github.com/bablilayoub/[email protected]
Advisory
Also known as: CVE-2026-54650, GO-2026-6135
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 filesEncoded 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.
High Basis: The source's own band: HIGH
0, fixed 0.1.2 (semver)0.1.2
0.1.2go get github.com/bablilayoub/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0