CVE-2026-59179

HIGH
MEDIUM Priority: 0.03 BB Relevance: 67/100
Published: 2026-10-28 Modified: 2026-10-29 First seen: 2026-10-29 Status: active

Attack Surface

Network Low Complexity No Auth Integ. Impact

CVSS Vector Breakdown

AV: Network
AC: Low
PR: None
UI: Required
S: Unchanged
C: Low
I: High
A: High

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.

Weakness Classification (1)

Affected Software (1)

VendorProductVersion
naorsabag openhop < 0.3.7

Bug Bounty Relevance

67 / 100
✓ Network accessible
✓ No authentication
✓ Low complexity

CVSS Score

8.3 / 10.0 v3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H

EPSS — Exploitation Probability

0.39%
Raw Score 0.003900
Percentile 33.1%
Date 2026-10-29

Intelligence Sources

mitre ref →
nvd ref →