{"answers":{"affected":"3 open source packages ship an affected version, including github.com/bablilayoub/openhole.","exploited":"There is no known exploitation of CVE-2026-54650 in the wild and no public exploit code.","fix":"Upgrade github.com/bablilayoub/openhole to 0.1.2 or later.","what":"CVE-2026-54650 is a high-severity path traversal vulnerability in bablilayoub openhole, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54650 and fix it if it is affected.\n\nWhat it is: CVE-2026-54650 is a high-severity path traversal vulnerability in bablilayoub openhole, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54650 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/bablilayoub/openhole (Go): affected all versions; fixed in 0.1.2\n- github.com/bablilayoub/openhole (Go): affected all versions; fixed in 0.1.2\n- github.com/bablilayoub/openhole (Go): affected all versions; fixed in 0.1.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54650/ (Markdown: https://insights.sbomify.com/CVE-2026-54650/index.md)","id":"CVE-2026-54650","markdown":"https://insights.sbomify.com/CVE-2026-54650/index.md","name":"CVE-2026-54650","record":{"aliases":["GHSA-fh2f-xfxc-q9cc","GO-2026-6135"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"openhole tunneling server","requires_auth":"none","summary":"An attacker can perform path traversal attacks against tunneled local services by exploiting improper URL path handling in openhole-server.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"openhole exposes localhost to the internet in one command. In 0.1.1 and earlier, openhole-server in internal/server/public_proxy.go forwarded r.URL.Path instead of preserving the original request target with r.URL.EscapedPath(), allowing percent encoded dot segments %2e and separators %2f to reach tunneled local services as ../ and / for path traversal. This issue is fixed in version 0.1.2.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"openhole-server vulnerable to path traversal via URL-decoded request path","id":"CVE-2026-54650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"pypdf: Possible infinite loop when processing threads/articles in writer","id":"CVE-2026-54651"},"packages":[{"ecosystem":"Go","fixed":["0.1.2"],"introduced":["0"],"last_affected":[],"package":"github.com/bablilayoub/openhole","purl":null,"source":"GHSA-fh2f-xfxc-q9cc"},{"ecosystem":"Go","fixed":["0.1.2"],"introduced":["0"],"last_affected":[],"package":"github.com/bablilayoub/openhole","purl":"pkg:golang/github.com/bablilayoub/openhole","source":"GHSA-fh2f-xfxc-q9cc"},{"ecosystem":"Go","fixed":["0.1.2"],"introduced":["0"],"last_affected":[],"package":"github.com/bablilayoub/openhole","purl":"pkg:golang/github.com/bablilayoub/openhole","source":"GO-2026-6135"}],"prev":{"headline":"Information disclosure in punchin-email","id":"CVE-2026-54649"},"products":["openhole"],"published":"2026-07-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-29","vendors":["bablilayoub"]},"summary":"An attacker can perform path traversal attacks against tunneled local services by exploiting improper URL path handling in openhole-server.","url":"https://insights.sbomify.com/CVE-2026-54650/"}