CVE-2026-100394

published 14 Oct 2026 · updated 29 Oct 2026

Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant

6.5MediumCVSS 6.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nezhahq>=2.2.7 <2.2.11

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-100394 severity on Zeptric[![CVE-2026-100394](https://zeptric.io/badge/cve/CVE-2026-100394.svg)](https://zeptric.io/cve/CVE-2026-100394)