---
id: CVE-2026-120046
title: >-
  Nezha 2.0.0 before 2.4.0 Startup NULL Pointer Dereference via Orphaned Service
  History
summary: >-
  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 /a…
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'
cvssSource: cna
cwe:
  - CWE-476
vendor: nezhahq
product: nezha
affected:
  - nezha >= 2.0.0 < 2.4.0
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T02:29:22.280402Z'
published: '2026-10-30'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T02:29:31.806Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-120046'
references:
  - url: >-
      https://github.com/nezhahq/nezha/commit/efd3e07b901d6acf7ef2ab3b26458cc07e7605dc
    label: Patch Commit
  - url: 'https://github.com/nezhahq/nezha/releases/tag/v2.4.0'
    label: nezha v2.4.0 Release Notes
  - url: >-
      https://github.com/nezhahq/nezha/blob/9881c47f0cc92256ba203919da5a25fab79a6bad/service/singleton/servicesentinel.go#L434
    label: loadTodayStats unchecked map dereference (2.3.18)
  - url: >-
      https://github.com/nezhahq/nezha/blob/9881c47f0cc92256ba203919da5a25fab79a6bad/cmd/dashboard/controller/service.go#L639
    label: Service deletion leaves service_histories rows (2.3.18)
  - url: 'https://github.com/nezhahq/nezha'
  - url: >-
      https://www.vulncheck.com/advisories/nezha-2.0.0-before-2.4.0-startup-null-pointer-dereference-via-orphaned-service-history
    label: >-
      VulnCheck Advisory: Nezha 2.0.0 before 2.4.0 Startup NULL Pointer
      Dereference via Orphaned Service History
tags:
  - cve.org
epss: 0.003
epssPercentile: 0.22831
ingestedAt: '2026-11-05T21:36:00.696Z'
---

## Overview

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.

## Affected

- `nezha >= 2.0.0 < 2.4.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.