CVE-2026-54650
openhole path traversal via percent-encoded segments exposes localhost publicly.
Is CVE-2026-54650 being exploited?
Not confirmed. CVE-2026-54650 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-54650?
CVE-2026-54650 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54650?
Yes. A fix has been recorded for CVE-2026-54650. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54650 affect?
CVE-2026-54650 affects openhole <= 0.1.1, openhole-server public_proxy.go, tunneled localhost services. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54650?
Upgrade to openhole v0.1.2 and block public access to localhost tunnels.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Percent-encoded %2e/%2f path traversal lets remote attackers reach localhost/tunneled services, exposing internal endpoints and enabling RCE on local apps.
Immediate action required
- affected< 0.1.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.