---
id: "CVE-2026-120046"
kind: "vulnerability"
aliases: ["CVE-2026-120046"]
title: "Nezha: deleting a service crashes the dashboard on next startup"
severity: "medium"
cvss: 6.0
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["monitoring", "nezha", "other", "self-hosted"]
not_affected_if: ["tsdb-storage", "version-2.4.0-or-later"]
published_at: "2026-10-30T19:18:22+00:00"
first_seen_at: "2026-10-30T19:25:29+00:00"
updated_at: "2026-10-30T19:26:30+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120046", "first_seen_at": "2026-10-30T19:25:29+00:00"}]
---

# Nezha: deleting a service crashes the dashboard on next startup

Nezha versions 2.0.0 before 2.4.0 have a NULL pointer dereference in ServiceSentinel.loadTodayStats. An authenticated user who deletes a service leaves orphaned service history rows that crash the non-TSDB dashboard on its next startup until those rows are removed manually.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Nezha dashboard version and confirm whether it is below `2.4.0`.
- Check whether the dashboard uses the non-TSDB storage mode (the sources do not name the setting).

## Fix

- Move to Nezha `2.4.0` or later.

## Timeline

- 2026-10-30T19:25:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-120046

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_