Skip to main content
VulnerabilityPublished Updated

CVE-2026-46716: nezhahq nezha · OS Command Injection

Affects nezhahq nezhaSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.8
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 12 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade nezha and nezhahq/nezha to 2.0.8.

Affected software

ProductAffectedFixed in
nezhahqnezhaAffected
  • >=1.4.0 <2.0.8
Fixed in
  • 2.0.8
GitHubnezhahq/nezhapkg:github/nezhahq/nezhaOther threatsAffected
  • >=1.4.0 <2.0.8
Fixed in
  • 2.0.8

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.8 or later, where this vulnerability is patched. No other mitigation or temporary workaround is documented. Patch status is confirmed by the vendor advisory indicating the fix in 2.0.8.

Description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.4.0 to before version 2.0.8, a RoleMember user can create a scheduled cron task with Cover=CronCoverAll, Servers=[] and an arbitrary Command. At every tick of the scheduler, the dashboard pushes that command to every server in the global ServerShared map — including servers that belong to other tenants (admin's servers, other members' servers). Each agent runs the command and returns the output, which is then sent to the attacker's own NotificationGroup → attacker-controlled webhook. This issue has been patched in version 2.0.8.

References

Community reviews

Loading reviews…