CVE-2026-100394: Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From 2.2.7 until 2.2.11, ServiceSentinel.worker in service/singleton/servicesentinel.go checked an owned service under servicesLock and later dereferenced pointer-valued serviceStatusToday and serviceCurrentStatusData entries under serviceResponseDataStoreLock without revalidating that ServiceSentinel.Delete had not removed them. A RoleMember could concurrently report TCP or ICMP results through the member's own agent and delete the same owned service, causing a nil pointer dereference. Because the gRPC server had no recovery interceptor, the worker panic terminated the whole dashboard process and disrupted every tenant's web interface, REST API, and agent connections. The issue affects availability only and does not disclose or modify data. This issue is fixed in versions 2.2.11 and 2.3.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Nezha Monitoringto a version that resolves this vulnerability.Fixed in 2.2.11 - Upgrade
Upgrade
Nezha Monitoringto a version that resolves this vulnerability.Fixed in 2.3.0
Event History
Frequently Asked Questions
Who can trigger the denial of service?
A user with the RoleMember role can trigger it, provided they can report TCP or ICMP results through their own agent and delete a service they own. No user interaction is required.
What is the operational impact if exploitation succeeds?
The panic terminates the entire dashboard process. This disrupts the web interface, REST API, and agent connections for every tenant; the issue affects availability only, not data confidentiality or integrity.
Which versions should be remediated?
Versions from 2.2.7 through 2.2.11 are affected according to the advisory. Fixed versions are 2.2.11 and 2.3.0.