CVE-2026-100394 · GHSA-qjpp-gffx-2wm9
Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant
- Risk score
- 56/100
- CVSS
- 6.5 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 14 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 entri…
- Affected
- github.com/nezhahq/nezha (go) >= 0.0.0-20260628010923-fd31e5f1b0f8, < 0.0.0-20260721131105-c893aa57867d
- Fix
- Upgrade github.com/nezhahq/nezha to 0.0.0-20260721131105-c893aa57867d or later.
- Exploitation
- Public proof of concept
Why it is Yellow
- CVSS 6.5 medium
- Public exploit or proof of concept referenced
- On your watchlist: Go
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| github.com/nezhahq/nezha | go | >= 0.0.0-20260628010923-fd31e5f1b0f8, < 0.0.0-20260721131105-c893aa57867d | 0.0.0-20260721131105-c893aa57867d |
References
- https://github.com/advisories/GHSA-qjpp-gffx-2wm9
- https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9
- https://nvd.nist.gov/vuln/detail/CVE-2026-100394
- 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
- https://github.com/advisories/GHSA-qjpp-gffx-2wm9
Original 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.
Last activity 14 Oct 2026. Patch Forecast updates every hour.