NVD / CVE Program· CNA GitHub_M

CVE-2026-62283: Nezha Monitoring: Cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: nezhahq nezha 2.0.10.

Low priority for now. Upgrade to nezhahq nezha 2.0.10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.9 · v3.1—No exploit Fix available

Broken access control (IDOR)

Published: Aug 21, 2026
Updated: Oct 12, 2026
EPSS: 0.5% · 46th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 9.9; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

nezhahq nezha
- >= 1.14.13, <= 1.14.14, >= 2.0.0, < 2.0.10affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/nezhahq/nezha	from 0	—
Go	github.com/nezhahq/nezha	from 1.14.13 · up to and including 1.14.14	—
Go	github.com/nezhahq/nezha	from 1.14.13	—
Go	github.com/nezhahq/nezha	from 2.0.0 · before 2.0.10	2.0.10

Same product

nezhahq: all records

Other highest-scoring records for the same primary product.

CVE-2026-46716Nezha Monitoring: RoleMember can run shell on every server (cross-tenant RCE) via POST /api/v1/cron
39Monitor
CVE-2026-101090Nezha through 2.2.3 Host Header Injection via OAuth2 redirect_uri
37Monitor
CVE-2026-53519Nezha Monitoring: Pre-auth path traversal via /dashboard.. prefix confusion leaks jwt_secret_key
37Monitor

Published before and after this one in the same product

← EarlierCVE-2026-53523Jun 12, 2026 · Nezha Monitoring: OAuth2 Redirect URL — Host Header Injection
27Monitor
← EarlierCVE-2026-59155Jul 10, 2026 · Nezha Monitoring: DDNS and Notification credential exposure via unredacted list API
27Monitor
Later →CVE-2026-101085Sep 27, 2026 · Nezha before 2.3.8 Denial of Service via Alert Rule
28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
nezhahq nezha	2.0.10 · description	Vendor (CNA)
Go:github.com/nezhahq/nezha	2.0.10	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

nezhahq/nezhacommit 6661d6a

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/nezhahq/nezha/commit/6661d6a7fc1c269f55c7f4e775082ad23fbe0f54

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records