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

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-q6xx-5vr8-p898, GO-2026-5821

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

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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


| Package | Ecosystem | 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.

## Is CVE-2026-62283 being exploited?

There is no known exploitation of CVE-2026-62283 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-62283 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected all versions; no fix listed
- github.com/nezhahq/nezha (Go): affected from 1.14.13; no fix listed
- github.com/nezhahq/nezha (Go): affected from 1.14.13 up to 1.14.14; no fix listed
- github.com/nezhahq/nezha (Go): affected from 1.14.13 up to 1.14.14; no fix listed
- github.com/nezhahq/nezha (Go): affected from 2.0.0; fixed in 2.0.10
- github.com/nezhahq/nezha (Go): affected from 2.0.0; fixed in 2.0.10

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-62283/ (Markdown: https://insights.sbomify.com/CVE-2026-62283/index.md)
```

## Sources

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

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