Skip to main content
VulnerabilityPublished

CVE-2026-59179: naorsabag openhop · Path Traversal

Affects naorsabag openhopSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High : upgrade to 0.3.7 soon.

Data as of 28 Oct 2026, 14:00 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.3.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade naorsabag openhop to 0.3.7.

Affected software

ProductAffectedFixed in
naorsabagopenhopAffected
  • <0.3.7
Fixed in
  • 0.3.7

AI-suggested

Upgrade OpenHop to version 0.3.7 or later, where this path traversal vulnerability is fixed. Until upgrading, restrict network access to the OpenHop server to trusted hosts only and consider tightening CORS policies to limit allowed origins. Review Docker deployment settings to avoid binding the service to all network interfaces if not necessary.

Description

OpenHop versions prior to 0.3.7 contain a path traversal vulnerability in the server component that allows unauthenticated attackers to read or delete YAML files outside the intended directory. This occurs because flow route parameters are passed without an identifier allow-list and are normalized by path.join after decodeURIComponent, enabling traversal. The vulnerability is exacerbated by permissive CORS settings and default Docker configurations that allow unauthenticated network access. This issue is fixed in version 0.3.7.

References

Community reviews

Loading reviews…