---
id: CVE-2026-100394
title: >-
  Nezha Monitoring is a self-hostable, lightweight, servers and websites
  monitoring and O&M tool
summary: >-
  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…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-362
  - CWE-476
published: '2026-10-14'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T16:17:28.820'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100394'
references:
  - url: >-
      https://github.com/nezhahq/nezha/commit/c893aa57867d8a3d608e2f2f16d1594c9766cdf3
    label: security-advisories@github.com
  - url: 'https://github.com/nezhahq/nezha/releases/tag/v2.2.11'
    label: security-advisories@github.com
  - url: 'https://github.com/nezhahq/nezha/releases/tag/v2.3.0'
    label: security-advisories@github.com
  - url: 'https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9'
    label: security-advisories@github.com
tags:
  - nvd
ingestedAt: '2026-10-14T16:40:32.109Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.