CVE-2026-100394: Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant
A single low-privilege RoleMember can take the entire Nezha dashboard offline, and with it every tenant’s web UI, REST API, and agent connections, by racing two ordinary operations on their own service. The crash is a nil pointer dereference in the service-monitor worker at service/singleton/servicesentinel.go:601. The worker checks a service exists under one lock and later writes to two pointer-valued status maps under a different lock; a concurrent delete removes the entries in the gap. Because the gRPC server has no recovery interceptor, the worker-goroutine panic kills the whole process. Availability only: nothing is read or modified.
References
- github.com/advisories/GHSA-qjpp-gffx-2wm9
- github.com/nezhahq/nezha/commit/c893aa57867d8a3d608e2f2f16d1594c9766cdf3
- github.com/nezhahq/nezha/releases/tag/v2.2.11
- github.com/nezhahq/nezha/releases/tag/v2.3.0
- github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9
- nvd.nist.gov/vuln/detail/CVE-2026-100394
Code Behaviors & Features
Detect and mitigate CVE-2026-100394 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →