Security readout for executives and security teams
Plain-English summary
A logged-in, low-privilege Nezha member who obtains another user’s live session identifier could take over that terminal or file-manager session. This could expose sensitive files, permit file modification, and enable commands on monitored servers. The issue is critical because one tenant’s access can cross into another user’s operational session.
Executive priority
Treat this as an urgent remediation for affected, multi-user Nezha deployments. Prioritize internet-accessible or broadly shared management installations because compromise could provide command execution and file access across monitored servers. Upgrade promptly and investigate possible identifier exposure or suspicious session activity.
Technical view
Affected Nezha releases verify only that a WebSocket stream UUID exists, not that it belongs to the requesting user. An authenticated RoleMember with a leaked live UUID can attach through the terminal or file WebSocket endpoints. This is an authorization failure categorized as CWE-639 and CWE-862, with CVSS 3.1 score 9.9.
Likely exposure
Exposure exists where Nezha 1.14.13–1.14.14 or 2.0.0–2.0.9 is deployed and untrusted or unnecessary RoleMember accounts can authenticate. Risk increases if live stream UUIDs enter logs, browser history, referrer data, or telemetry accessible to those users.
Exploitation context
Exploitation requires authentication as a RoleMember and possession of a valid, live stream UUID. The supplied sources identify several possible UUID leakage channels. They do not establish active exploitation in the wild, and the CVE is not identified as being in KEV.
Researcher notes
The vulnerable authorization model binds access to UUID existence rather than stream ownership. Impact spans confidentiality, integrity, and availability because terminal and file-manager streams permit interactive server operations. The supplied material confirms affected ranges and the 2.0.10 fix, but provides no evidence of public or in-the-wild exploitation.
Mitigation direction
- Upgrade affected deployments to Nezha 2.0.10 or later following vendor guidance.
- Restrict RoleMember access to trusted, operationally necessary accounts until upgrading.
- Protect logs and telemetry that may contain live stream UUIDs from member access.
- Review vendor advisory and release notes before completing the production rollout.
Validation and detection
- Inventory Nezha deployments and compare installed versions with the affected ranges.
- Confirm every upgraded instance reports version 2.0.10 or later.
- Review RoleMember accounts and remove access that is no longer required.
- Check logs and telemetry for exposure of live stream UUIDs.
- Investigate unexpected cross-user session attachments, file changes, or shell activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-62283 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/nezhahq/nezha/security/advisories/GHSA-q6xx-5vr8-p898CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/nezhahq/nezha/commit/6661d6a7fc1c269f55c7f4e775082ad23fbe0f54CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/nezhahq/nezha/releases/tag/v2.0.10CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.