Skip to content

← Actionable
Medium, CVSS 6.5

Nezha Monitoring: Nezha WebSocket server stream discloses cross-tenant server telemetry to authenticated members

CVE-2026-47124GHSA-hvv7-hfrh-7gxj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/nezhahq/nezha 1.14.15-0.20260517034128-05e5da253519), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/nezhahq/nezha

    Affected
    >= 1.4.0, < 1.14.15-0.20260517034128-05e5da253519
    Fixed in
    1.14.15-0.20260517034128-05e5da253519

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-47124: 0.34% estimated exploitation activity in the next 30 days; percentile 27.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Any authenticated non-admin member can connect to the server-status WebSocket and receive telemetry for all servers, including servers owned by other users. The normal server list API filters objects by HasPermission, but the WebSocket stream treats the presence of any authenticated user as authorization for the full unfiltered server list. Details The server WebSocket route is registered under the optional-auth group in cmd/dashboard/controller/controller.go:71-73: serverStream treats any CtxKeyAuthorizedUser as a member, without checking admin role or per-server ownership, in cmd/dashboard/controller/ws.go:123-139: The authorization boolean is then used as a full/guest switch in getServerStat in cmd/dashboard/controller/ws.go:160-184: For authenticated members, GetSortedList() returns all servers and server.Host is not filtered. There is no call to server.HasPermission(c). The streamed response model in model/serverapi.go:5-20 includes server ID/name, public note, host…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-hvv7-hfrh-7gxj

Agent brief

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

# Patch Next advisory brief: CVE-2026-47124

Advisory: Nezha Monitoring: Nezha WebSocket server stream discloses cross-tenant server telemetry to authenticated members
IDs: CVE-2026-47124, GHSA-hvv7-hfrh-7gxj
Record: https://patchnext.com/advisories/cve-2026-47124 (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: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/nezhahq/nezha 1.14.15-0.20260517034128-05e5da253519. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nezhahq/nezha: affected >= 1.4.0, < 1.14.15-0.20260517034128-05e5da253519; fixed in 1.14.15-0.20260517034128-05e5da253519

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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-hvv7-hfrh-7gxj (GitHub-reviewed advisory GHSA-hvv7-hfrh-7gxj lists affected ranges: Go github.com/nezhahq/nezha >=1.4.0 <1.14.15-0.20260517034128-05e5da253519)

Commands are suggestions: review each one before running it.

Loading voting…