Nezha vulnerable to cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary In nezha v1.14.13–v1.14.14 and v2.0.0–v2.0.9, the WebSocket endpoints GET /ws/terminal/:id and GET /ws/file/:id authenticate the caller only by the presence of a valid stream UUID, with no ownership check tying that UUID to the user who created the stream. Any authenticated dashboard user (including a RoleMember) who learns a live stream UUID can attach to the session and gain interactive shell access or full file-manager control on the target server — i.e. cross-tenant RCE. This was silently fixed in commit 6661d6a (2026-05-18, shipped in v2.0.10). At submission time no public CVE/GHSA covers this fix, so operators of v1.14.x and pre-v2.0.10 v2.x deployments have no signal that they are running vulnerable code. Details Stream allocation — service/rpc/iostream.go (v2.0.9): No creator is bound to the stream. Stream attach — cmd/dashboard/controller/terminal.go (v2.0.9): The only authorization check is GetStream(streamId) — "does this UUID exist in the in-memory map". getUid(c)…

Published by the source

26 Jun 2026, 22:31 UTC

Last modified by the source

26 Jun 2026, 22:31 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q6xx-5vr8-p898

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-q6xx-5vr8-p898

Advisory: Nezha vulnerable to cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check
IDs: GHSA-q6xx-5vr8-p898
Record: https://patchnext.com/advisories/ghsa-q6xx-5vr8-p898 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/nezhahq/nezha 2.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nezhahq/nezha: affected >= 1.14.13, <= 1.14.14; >= 2.0.0, <= 2.0.9; fixed in 2.0.10

## Suggested inspection (read-only)
- Go github.com/nezhahq/nezha: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/nezhahq/nezha.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q6xx-5vr8-p898 (GitHub-reviewed advisory GHSA-q6xx-5vr8-p898 lists affected ranges: Go github.com/nezhahq/nezha >=1.14.13 =2.0.0 <=2.0.9)

Commands are suggestions: review each one before running it.