Nezha 2.0.0 before 2.4.0 contains a NULL pointer dereference vulnerability in ServiceSentinel.loadTodayStats that allows authenticated users to crash the dashboard by deleting a service. Attackers can delete their own service via POST /api/v1/batch-delete/service, leaving orphaned service_histories rows that crash the non-TSDB dashboard on its next startup until removed manually.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.0 · nezhahqNVD modified 2026-10-30 18:52
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/nezhahq/nezha/commit/efd3e07b901d6acf7ef2ab3b26458cc07e7605dc patch
- https://github.com/nezhahq/nezha/releases/tag/v2.4.0 release-notes
- https://github.com/nezhahq/nezha/blob/9881c47f0cc92256ba203919da5a25fab79a6bad/service/singleton/servicesentinel.go#L434 technical-description
- https://github.com/nezhahq/nezha/blob/9881c47f0cc92256ba203919da5a25fab79a6bad/cmd/dashboard/controller/service.go#L639 technical-description
- https://github.com/nezhahq/nezha product
- https://www.vulncheck.com/advisories/nezha-2.0.0-before-2.4.0-startup-null-pointer-dereference-via-orphaned-service-history third-party-advisory