CVE-2026-100394
Nezha Monitoring is a self-hostable, lightweight, servers and …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/nezhahq/nezha/commit/c893aa57867d8a3d608e2f2f16d1594c9766cdf3
- github.com/nezhahq/nezha/releases/tag/v2.2.11
- github.com/nezhahq/nezha/releases/tag/v2.3.0
- github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9
- nvd.nist.gov/vuln/detail/CVE-2026-100394
- github.com/advisories/GHSA-qjpp-gffx-2wm9
- nvd.nist.gov/vuln/detail/CVE-2026-100394
- cve.org/CVERecord?id=CVE-2026-100394
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.