Vulnerabilities in pkg:golang/github.com/bablilayoub/openhole

PACKAGE
Advisory Identifier: GHSA-fh2f-xfxc-q9cc
Share
Advisory Summary

CVE-2026-54650 is a HIGH (CVSS 8.6) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/bablilayoub/openhole libraries in the Go ecosystem. The issue involves openhole-server vulnerable to path traversal via url-decoded request path. Remediation is available by upgrading affected packages to version 0.1.2.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/bablilayoub/openhole

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/bablilayoub/openhole. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fh2f-xfxc-q9cc CVE-2026-54650 HIGH openhole-server vulnerable to path traversal via URL-decoded request path

CVE-2026-54650 at a Glance

CVE Identifier CVE-2026-54650
GHSA Identifier GHSA-fh2f-xfxc-q9cc
Severity HIGH
CVSS v3.1 Base Score 8.6
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Github.com/bablilayoub/openhole
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-54650

To remediate this vulnerability, upgrade all affected Github.com/bablilayoub/openhole dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/bablilayoub/openhole fixed: 0.1.2 
Upgrade github.com/bablilayoub/openhole to 0.1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/bablilayoub/openhole

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-54650, inspect your project dependencies for Github.com/bablilayoub/openhole:

inspect dependencies for github.com/bablilayoub/openhole

Analyze the terminal output to locate any version of Github.com/bablilayoub/openhole in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Github.com/bablilayoub/openhole, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

CVE-2026-54650 Affected Github.com/bablilayoub/openhole Versions

1 component(s)
Fixed Versions:
0.1.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/bablilayoub/openhole
golang/github.com/bablilayoub/openhole
Go
< 0.1.2
0.1.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/bablilayoub/openhole/security/advisories/GHSA-fh2f-xfxc-q9cc
Security Fix Commit FIX COMMIT
https://github.com/bablilayoub/openhole/commit/a28c27adde2a7ed0c347b730c8707208c0f78ed3
Github.com/bablilayoub/openhole Source Repository REPOSITORY
https://github.com/bablilayoub/openhole
Github.com/bablilayoub/openhole Release RELEASE
https://github.com/bablilayoub/openhole/releases/tag/v0.1.2

Frequently Asked Questions

What is CVE-2026-54650?
CVE-2026-54650 is a security vulnerability in Github.com/bablilayoub/openhole involving openhole-server vulnerable to path traversal via URL-decoded request path under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Github.com/bablilayoub/openhole versions are affected?
Affected versions include releases prior to 0.1.2 across affected packages: github.com/bablilayoub/openhole.
What version fixes CVE-2026-54650?
Upgrading to 0.1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/bablilayoub/openhole affected?
Yes, github.com/bablilayoub/openhole is affected in releases prior to 0.1.2. Upgrade your dependency to 0.1.2 or later.
What is the CVSS score of CVE-2026-54650?
CVE-2026-54650 has a CVSS v3.1 base score of 8.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-54650?
CVE-2026-54650 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Go dependencies for CVE-2026-54650?
Run the dependency tree command: 'inspect dependencies for github.com/bablilayoub/openhole'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fh2f-xfxc-q9cc",
  "modified" : "2026-07-28T22:20:51Z",
  "published" : "2026-07-28T22:20:51Z",
  "aliases" : [ "CVE-2026-54650" ],
  "summary" : "openhole-server vulnerable to path traversal via URL-decoded request path",
  "details" : "## Summary\n\nopenhole-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.\n\nGo's ServeMux rejects literal `../` paths, but percent-encoded traversal sequences bypassed this and were delivered to backends as working path traversal.\n\n## Impact\n\nAn unauthenticated remote attacker could read files outside the published web root on tunneled local services that resolve paths without canonicalization.\n\nExample:\n- `/%2e%2e/secret.txt` → file outside web root\n- `/%2e%2e/%2e%2e/etc/passwd` → sensitive files\n\nEncoded slashes (`/a%2fb`) could also bypass path-based access controls.\n\n## Fix\n\nv0.1.2 forwards `r.URL.EscapedPath()` on the server and preserves the request-target on the CLI client.\n\nUsers should upgrade both openhole-server and the openhole CLI to v0.1.2 or later.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/bablilayoub/openhole"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.1.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bablilayoub/openhole/security/advisories/GHSA-fh2f-xfxc-q9cc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bablilayoub/openhole/commit/a28c27adde2a7ed0c347b730c8707208c0f78ed3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bablilayoub/openhole"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bablilayoub/openhole/releases/tag/v0.1.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-28T22:20:51Z",
    "nvd_published_at" : null
  }
}