CVE-2026-59179: OpenHop: Path Traversal in Flow ID File Operations
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
OpenHop is a tool for creating interactive data-flow diagrams. Prior to 0.3.7, `@openhop/server` passes unauthenticated flow route parameters from `GET /api/flows/:id` and `DELETE /api/flows/:id` in `packages/server/src/routes.ts` to `FlowStore.filePath()` in `packages/server/src/store.ts` without an identifier allow-list. The router applies `decodeURIComponent` to the id, and `path.join()` then normalizes traversal outside the configured flow directory after appending the .yaml extension. An attacker can read accessible YAML files as YAML-parsed JSON or permanently delete accessible .yaml files outside that directory, exposing configuration or secrets and disrupting dependent services. In `packages/server/src/index.ts`, CORS `origin: true` permits any browser origin, enabling a malicious webpage to target a loopback-bound instance. Docker deployments default to `HOST=0.0.0.0` and permit direct unauthenticated network access. This issue is fixed in repository release 0.3.7.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-28).
Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality low, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 7 references on Exploit Observer
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| naorsabag openhop | version < 0.3.7 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-59179 OpenHop Unauthenticated Path Traversal via /api/flows. Add them to your Suricata rule set and reload.
Show the rules
# CVE-2026-59179 - OpenHop @openhop/server (< 0.3.7) unauthenticated path traversal
# (CWE-22) in GET/DELETE /api/flows/:id. The find-my-way router percent-decodes the id
# and FlowStore.filePath() joins it into the flow directory before appending ".yaml", so
# a traversal id such as "..%2Fvictim" escapes the directory to read (as YAML-parsed JSON)
# or delete arbitrary .yaml files. Matches a ".." segment immediately after /api/flows/,
# encoded or raw, on the as-sent (raw) request URI.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-59179 OpenHop Unauthenticated Path Traversal via /api/flows"; flow:established,to_server; http.uri.raw; content:"/api/flows/"; nocase; fast_pattern; pcre:"/\/api\/flows\/[^\x20\x23\x3f]*?\x2e\x2e(?:\x2f|\x5c|%2f|%5c|%252f|%255c)/i"; classtype:web-application-attack; reference:cve,CVE-2026-59179; reference:url,https://www.exploit.observer/?keyword=CVE-2026-59179&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=openhop&match=exact; sid:1091001; rev:1;)
CVE-2026-59179.rules on GitHub
References
Other references
- https://github.com/naorsabag/openhop/security/advisories/GHSA-g72f-jw3w-mgh7 (x_refsource_CONFIRM)
- https://github.com/naorsabag/openhop/pull/190 (x_refsource_MISC)
- https://github.com/naorsabag/openhop/commit/c8190fbefa3a50e7b0c16c001d2e05b0e920cfb4 (x_refsource_MISC)
- https://github.com/naorsabag/openhop/releases/tag/v0.3.7 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
