p PatchFirst

CVE-2026-100394

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 6.5 · Medium · EPSS 0.4%

Published
Updated

Affected products and versions

  • nezha

    Versions
    • >= 2.2.7, < 2.2.11: Affected

    No fix published

Original sources

Check your server →