CVE-2026-100394

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.
Configurations

No configuration.

History

29 Oct 2026, 15:17

Type Values Removed Values Added
References () https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9 - () https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9 -

14 Oct 2026, 16:17

Type Values Removed Values Added
New CVE

Information

Published : 2026-10-14 16:17

Updated : 2026-10-29 15:17


NVD link : CVE-2026-100394

Mitre link : CVE-2026-100394

CVE.ORG link : CVE-2026-100394


JSON object : View

Products Affected

No product.

CWE
CWE-362

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CWE-476

NULL Pointer Dereference