cve.bz

CVE-2026-62283 nezhahq nezha: Missing Authorization

9.9 criticalEPSS 0.6%Fix available

Critical (9.9) in nezhahq nezha. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/nezhahq/nezha 2.0.10.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-639 Authorization Bypass Through User-Controlled Key
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/nezhahq/nezha (Go): fixed in 2.0.10

Ask an AI about this CVE

Show the promptExplain CVE-2026-62283 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62283?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62283?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62283 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nezhahq nezha>= 1.14.13, <= 1.14.14
nezhahq nezha>= 2.0.0, < 2.0.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q6xx-5vr8-p898Gogithub.com/nezhahq/nezha>=1.14.13 <=1.14.14no fix published
GHSA-q6xx-5vr8-p898Gogithub.com/nezhahq/nezha>=2.0.0 <2.0.102.0.10
GO-2026-5821Gogithub.com/nezhahq/nezhaall versionsno fix published
GO-2026-5821Gogithub.com/nezhahq/nezha>=1.14.13no fix published

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON