CVE-2026-62283 Nezha Monitoring: Cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check
Authenticated users can hijack other users' terminal and file sessions by guessing stream UUIDs, leading to remote code execution and data access.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-62283?
CVE-2026-62283 is a critical missing authorization vulnerability in nezhahq nezha, published on 21 Aug 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. Nezha versions 1.14.13 through 1.14.14 and 2.0.0 through 2.0.9 do not bind stream identifiers created by CreateStream in service/rpc/io_stream.go to their creating user, and `GET /ws/terminal/:id` and `GET /ws/file/:id` only check whether the supplied UUID exists. An authenticated RoleMember who obtains a live stream UUID from logs, browser history, referer data, or telemetry can attach to another user's terminal or file-manager session, read and write target-server files, and execute shell commands. This issue is fixed in version 2.0.10.
Which versions are affected by CVE-2026-62283?
6 open source packages ship an affected version, including github.com/nezhahq/nezha.
| Package | Affected | Fixed in |
|---|---|---|
github.com/nezhahq/nezha Go | All versions | None |
github.com/nezhahq/nezha Go | From 1.14.13 | None |
github.com/nezhahq/nezha Go | From 1.14.13 to 1.14.14 | None |
github.com/nezhahq/nezha Go | From 1.14.13 to 1.14.14 | None |
github.com/nezhahq/nezha Go | From 2.0.0 | 2.0.10 |
github.com/nezhahq/nezha Go | From 2.0.0 | 2.0.10 |
How do I fix CVE-2026-62283?
Upgrade github.com/nezhahq/nezha to 2.0.10 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-62283 being exploited?
There is no known exploitation of CVE-2026-62283 in the wild and no public exploit code.
Sources
Also known as GHSA-q6xx-5vr8-p898, GO-2026-5821.