openhole-server vulnerable to path traversal via URL-decoded request path — CVE-2026-54650

Summary

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

Timeline

Published by source

2026-07-29

Risk context

• Reported severity or threat level: high.
• Review exposure for the affected product or family: go: github.com/bablilayoub/openhole.

Product

go: github.com/bablilayoub/openhole

What to do

General, cautious steps (verify details in the official source):

• Prioritize patching or mitigation immediately (treat as actively risky).
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source
• CVE Record
• NVD

Evidence and provenance

Canonical advisory ID

CVE-2026-54650

Source

GitHub

Vendor

GitHub

Published by source

2026-07-29

Last source activity

2026-07-29

Additional identifiers

GHSA-FH2F-XFXC-Q9CC

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.