Advisory record · GHSA-hvv7-hfrh-7gxj

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

CVSS 6.5 MediumEPSS 0.0034 · 27th percentile

Published by the GitHub Advisory Database at 23 May 2026, 00:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nezhahq/nezhaGo>=1.4.0, <1.14.15-0.20260517034128-05e5da2535191.14.15-0.20260517034128-05e5da253519
Identifiers
GHSA-hvv7-hfrh-7gxj · CVE-2026-47124 · GO-2026-5439
Weakness (CWE)
CWE-200
Published
23 May 2026
Updated
26 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nezha (Go package github.com/nezhahq/nezha) before 1.14.15-0.20260517034128-05e5da253519 has a flaw in its server-status WebSocket stream. Any authenticated non-admin member can connect and receive telemetry for all servers, including servers owned by other users, because the stream does not apply the per-owner filtering that the normal server list API uses. An attacker with a member account can therefore monitor other tenants' server inventory and live resource data. Upgrade to 1.14.15-0.20260517034128-05e5da253519 or later. The source gives no workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.