CVE-2026-54650

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

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.

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-54650 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2026-54650? CVE-2026-54650 is a high-severity path traversal vulnerability in github.com/bablilayoub/openhole (go), affecting versions <= 0.1.1. It is fixed in 0.1.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-54650? CVE-2026-54650 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/bablilayoub/openhole are affected by CVE-2026-54650? github.com/bablilayoub/openhole (go) versions <= 0.1.1 is affected.
4. Is there a fix for CVE-2026-54650? Yes. CVE-2026-54650 is fixed in 0.1.2. Upgrade to this version or later.
5. Is CVE-2026-54650 exploitable, and should I be worried? Whether CVE-2026-54650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54650 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54650? Upgrade github.com/bablilayoub/openhole to 0.1.2 or later.