CVE-2026-54650

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 29, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v0.1.2

Patch available: bablilayoub/openhole v0.1.2

https://github.com/bablilayoub/openhole/releases/tag/v0.1.2
github_commit Patch Available

commit a28c27adde2a (bablilayoub/openhole)

Patch available: bablilayoub/openhole v0.1.2 (contains commit a28c27adde2a)

https://github.com/bablilayoub/openhole/commit/a28c27adde2a7ed0c347b730c8707208c0f78ed3
github Patch Available

Path traversal via URL-decoded request path in openhole-server · Advisory · bablilayoub/openhole · GitHub

https://github.com/bablilayoub/openhole/security/advisories/GHSA-fh2f-xfxc-q9cc

Vendor Advisories for CVE-2026-54650(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/bablilayoub/openhole—0.1.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 56× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 23:27 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 21:40 UTCEG score recompute
  4. 2026-08-23 06:42 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 05:02 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 03:20 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 00:43 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 22:59 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 21:20 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 19:41 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 06:51 UTCEG score recompute
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 05:12 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 03:32 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 01:52 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 31 more
  1. 2026-08-12 00:13 UTCEG score recompute
  2. 2026-08-11 11:23 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 20:55 UTCEG score recompute
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 19:16 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 17:37 UTCEG score recompute
  9. 2026-08-06 15:57 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-06 03:07 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 01:27 UTCEG score recompute
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 12:38 UTCEG score recompute
  16. 2026-08-04 10:39 UTCEPSS rescore
  17. 2026-08-03 10:59 UTCEG score recompute
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 09:17 UTCEG score recompute
  20. 2026-08-02 02:27 UTCEPSS rescore
  21. 2026-08-01 07:38 UTCEG score recompute
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 17:05 UTCEG score recompute
  24. 2026-07-30 16:28 UTCEPSS rescore
  25. 2026-07-30 04:13 UTCEG score recompute
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 15:24 UTCEG score recompute
  28. 2026-07-29 14:49 UTCEG score recompute
  29. 2026-07-28 23:22 UTCEG score recompute
  30. 2026-07-28 22:46 UTCEG score recompute
  31. 2026-07-28 22:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54650?
CVE-2026-54650 is a high vulnerability published on July 28, 2026. 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…
When was CVE-2026-54650 disclosed?
CVE-2026-54650 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54650 actively exploited?
CVE-2026-54650 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.2% of all scored CVEs.
What is the CVSS score of CVE-2026-54650?
CVE-2026-54650 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-54650?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54650, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54650

Explore →

Is Your Infrastructure Affected by CVE-2026-54650?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs