CVE-2026-54650 is a high-severity (CVSS 8.6) Path Traversal vulnerability in github.com/bablilayoub/openhole. A fix is available for github.com/bablilayoub/openhole — see the affected versions and patch details below.
openhole-server vulnerable to path traversal via URL-decoded request path
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-54650.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-54650 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 396,257 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/bablilayoub/openholeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/bablilayoub/openhole | all versions | 0.1.2go get github.com/bablilayoub/openhole@v0.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bablilayoub/openhole, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bablilayoub/openhole to 0.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54650 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2026-54650 in your dependencies?
Find it across Go, including transitive dependencies.