# CVE-2026-47124: Nezha WebSocket server stream discloses cross-tenant server telemetry to authenticated members

> Authenticated non-admin users can access cross-tenant server telemetry via WebSocket, exposing sensitive monitoring data to unauthorized members.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-hvv7-hfrh-7gxj, GO-2026-5439

## What is CVE-2026-47124?

CVE-2026-47124 is a medium-severity missing authorization vulnerability in nezhahq nezha, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.4.0 to before version 2.0.9, 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. This issue has been patched in version 2.0.9.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-47124?

3 open source packages ship an affected version, including github.com/nezhahq/nezha.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/nezhahq/nezha` | Go | From 1.4.0 | 1.14.15-0.20260517034128-05e5da253519 |
| `github.com/nezhahq/nezha` | Go | From 1.4.0 | 1.14.15-0.20260517034128-05e5da253519 |
| `github.com/nezhahq/nezha` | Go | From 1.4.0 | 1.14.15-0.20260517034128-05e5da253519 |

## How do I fix CVE-2026-47124?

Upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517034128-05e5da253519 or later.

## Is CVE-2026-47124 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47124 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47124 and fix it if it is affected.

What it is: CVE-2026-47124 is a medium-severity missing authorization vulnerability in nezhahq nezha, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47124 exists.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected from 1.4.0; fixed in 1.14.15-0.20260517034128-05e5da253519
- github.com/nezhahq/nezha (Go): affected from 1.4.0; fixed in 1.14.15-0.20260517034128-05e5da253519
- github.com/nezhahq/nezha (Go): affected from 1.4.0; fixed in 1.14.15-0.20260517034128-05e5da253519

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47124/ (Markdown: https://insights.sbomify.com/CVE-2026-47124/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47124
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47124
- OSV: https://osv.dev/vulnerability/CVE-2026-47124

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47124/
Summaries are generated and may contain mistakes; the official description above is the record.