CVE-2026-46716
Received Received - Intake
Stored Command Injection in Nezha Monitoring

Publication date: 2026-06-12

Last updated on: 2026-06-12

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-12
Last Modified
2026-06-12
Generated
2026-06-13
AI Q&A
2026-06-13
EPSS Evaluated
N/A
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nezha_monitoring nezha_monitoring From 1.4.0 (inc) to 2.0.8 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-78 The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
CWE-269 The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Nezha Monitoring versions from 1.4.0 up to before 2.0.8. A user with RoleMember privileges can create a scheduled cron task with specific parameters (Cover=CronCoverAll, Servers=[]) and an arbitrary command. When the scheduler runs, it pushes this command to every server in the global ServerShared map, including servers belonging to other tenants such as admins or other members.

Each agent on these servers executes the command and returns the output, which is then sent to the attacker's NotificationGroup via an attacker-controlled webhook. This allows the attacker to run arbitrary commands across multiple servers they should not have access to.

This issue was fixed in version 2.0.8.

Impact Analysis

This vulnerability can have severe impacts including unauthorized remote code execution on multiple servers across different tenants. An attacker can run arbitrary commands on servers they do not own or manage, potentially leading to data theft, system compromise, or disruption of services.

Because the attacker receives the output of these commands, sensitive information from other tenants' servers can be exposed. The vulnerability also allows for high integrity and availability impact, meaning attackers could alter or disrupt system operations.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade Nezha Monitoring to version 2.0.8 or later, where the issue has been patched.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46716. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart