Path Traversal in github.com/bablilayoub/openhole (CVE-2026-54650)
Summary
Path traversal in github.com/bablilayoub/openhole (CVE-2026-54650). Confidential information can be exposed externally. Exploitable via r.URL.Path. Mitigation: upgrade to 0.1.2 or later.
Original description
The description as published by the source.
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: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54650 has been found in github.com/bablilayoub/openhole.
Attackers can target a specific entry point like r.URL.Path over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade github.com/bablilayoub/openhole to 0.1.2 or later.
If unsure, ask your IT team or search "github.com/bablilayoub/openhole CVE-2026-54650" on the vendor's site.
CVE-2026-54650 (github.com/bablilayoub/openhole) — CWE-22 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: r.URL.Path
Patched: 0.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/bablilayoub/openhole. Attackers reach the vulnerable code path via r.URL.Path without authentication.
Check the vendor advisory for the affected versions of github.com/bablilayoub/openhole. Attack surface: r.URL.Path.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 0.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/bablilayoub/openhole' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/bablilayoub/openhole' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/bablilayoub/openholeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/bablilayoub/openhole to 0.1.2ステージング環境で 0.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com