# CVE-2026-54650 — bablilayoub openhole

> As of 2026-07-28, CVE-2026-54650 is a HIGH-severity vulnerability in bablilayoub openhole, CVSS v3.1 8.6. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-54650 as of 2026-07-28; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-28

## What is CVE-2026-54650?

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.

The record classifies CVE-2026-54650 under weakness class [CWE-22](https://intel.threadlinqs.com/cwe/CWE-22). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 69 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.6 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-28

## Is CVE-2026-54650 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **bablilayoub**: openhole

## How to fix CVE-2026-54650

No vendor patch reference has been recorded for CVE-2026-54650 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-54650

No threat campaign in the Threadlinqs corpus currently references CVE-2026-54650, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-07-30. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/bablilayoub/openhole/security/advisories/GHSA-fh2f-xfxc-q9cc)

**Other references**

- [github.com](https://github.com/bablilayoub/openhole/commit/a28c27adde2a7ed0c347b730c8707208c0f78ed3)
- [github.com (v0.1)](https://github.com/bablilayoub/openhole/releases/tag/v0.1.2)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-54650
Full detection coverage and IOCs for threats exploiting CVE-2026-54650 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp