Skip to main content
VulnerabilityPublished

CVE-2026-62283: nezhahq nezha · Insecure Direct Object Reference

Affects nezhahq nezhaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 2.0.10 as a priority.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade nezha and nezhahq/nezha to 2.0.10.

Affected software

ProductAffectedFixed in
nezhahqnezhaAffected
  • >=1.14.13 <=1.14.14
  • >=2.0.0 <2.0.10
Fixed in
  • 2.0.10
GitHubnezhahq/nezhapkg:github/nezhahq/nezhaOther threatsAffected
  • =1.14.13
  • =1.14.14
  • >=2.0.0 <2.0.10
Fixed in
  • 2.0.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Nezha Monitoring to version 2.0.10 or later, where this vulnerability is fixed. There is no indication of any temporary workaround or mitigation other than applying the official fix.

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.

References

Community reviews

Loading reviews…