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

Advisory record · `GHSA-hvv7-hfrh-7gxj`

- **Identifiers:** `GHSA-hvv7-hfrh-7gxj` · `CVE-2026-47124` · `GO-2026-5439`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 23 May 2026
- **Updated:** 26 Jun 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/nezhahq/nezha` (Go): affected `>=1.4.0, <1.14.15-0.20260517034128-05e5da253519`; fixed in `1.14.15-0.20260517034128-05e5da253519`

## 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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from 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

- 31 Oct 2026, 15:06 UTC: First seen by agentprime
- 31 Oct 2026, 15:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hvv7-hfrh-7gxj)

## Sources

- [GitHub Advisory Database: GHSA-hvv7-hfrh-7gxj](https://github.com/advisories/GHSA-hvv7-hfrh-7gxj)
- [OSV: GHSA-hvv7-hfrh-7gxj](https://osv.dev/vulnerability/GHSA-hvv7-hfrh-7gxj)
- <https://github.com/nezhahq/nezha/security/advisories/GHSA-hvv7-hfrh-7gxj>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-47124>
- <https://github.com/nezhahq/nezha>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hvv7-hfrh-7gxj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hvv7-hfrh-7gxj/>. Everything for agents: <https://agentprime.io/llms.txt>.
