CVE-2026-62283

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 21, 2026

Last Modified

August 21, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check · Advisory · nezhahq/nezha · GitHub

https://github.com/nezhahq/nezha/security/advisories/GHSA-q6xx-5vr8-p898
github_release Patch Available

v2.0.10

Patch available: nezhahq/nezha v2.0.10

https://github.com/nezhahq/nezha/releases/tag/v2.0.10
github_commit

commit 6661d6a7fc1c (nezhahq/nezha)

Fix landed in nezhahq/nezha commit 6661d6a7fc1c — awaiting tagged release

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/nezhahq/nezha—2.0.10—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-23 00:23 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 22:25 UTCEG score recompute
  4. 2026-08-21 21:51 UTCEG score recompute
  5. 2026-08-21 21:24 UTCEG score recompute
  6. 2026-08-21 20:34 UTCEG score recompute
  7. 2026-08-21 20:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62283?
CVE-2026-62283 is a critical vulnerability published on August 21, 2026. 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…
When was CVE-2026-62283 disclosed?
CVE-2026-62283 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62283 actively exploited?
CVE-2026-62283 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-62283?
CVE-2026-62283 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-62283?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62283, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62283

Explore →

Is Your Infrastructure Affected by CVE-2026-62283?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs