CVE-2026-100394
Description
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.
How to fix
- github.com/nezhahq/nezha0.0.0-20260721131105-c893aa57867d or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| github.com/nezhahq/nezhaGo | 0.0.0-20260628010923-fd31e5f1b0f8 ≤ v < 0.0.0-20260721131105-c893aa57867d | 0.0.0-20260721131105-c893aa57867d |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.