Answer in brief
CVE-2026-54650 records a High severity path traversal vulnerability in openhole-server vulnerable to path traversal via URL-decoded request path. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-54650 records a High severity path traversal vulnerability in openhole-server vulnerable to path traversal via URL-decoded request path. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update github.com/bablilayoub/openhole to 0.1.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPath Traversal describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54650 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/bablilayoub/openholego | <=0.1.1 | 0.1.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54650 records a High severity path traversal vulnerability in openhole-server vulnerable to path traversal via URL-decoded request path. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for github.com/bablilayoub/openhole.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate github.com/bablilayoub/openhole to 0.1.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPath Traversal describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54650 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/bablilayoub/openholego | <=0.1.1 | 0.1.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54650 records a High severity path traversal vulnerability in openhole-server vulnerable to path traversal via URL-decoded request path. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for github.com/bablilayoub/openhole.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard## 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.
## 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.