Nezha before 2.3.8 Denial of Service via Alert Rule (CVE-2026-101085) | HOL Guard CVE

High · CVSS 7.1CVE-2026-101085

Nezha before 2.3.8 Denial of Service via Alert Rule

Answer in brief

CVE-2026-101085 records a High severity (CVSS 7.1) vulnerability in Nezha before 2.3.8 Denial of Service via Alert Rule. The current sources do not mark it as known exploited. The current feed maps nezhahq/nezha (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 27, 2026Updated Sep 27, 2026Source checked Sep 28, 2026First seen by HOL Sep 27, 2026Material review Sep 27, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nezhahq/nezha (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nezhahq/nezhageneric	>=0 <2.3.8	2.3.8

Recommended response

Check inventory. Check lockfiles and deployed manifests for nezhahq/nezha.
Review the reported fix. Update nezhahq/nezha to 2.3.8 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 27, 2026

Sources and claim methodology

Upstream source description

Nezha before 2.3.8 fails to validate alert rule type and duration bounds, allowing authenticated non-administrator users to create malformed rules that trigger unrecovered panics in the alert evaluator goroutine. Attackers can submit a crafted alert rule via the POST /api/v1/alert-rule endpoint to crash the dashboard process, which persists the rule and causes repeated crashes on restart, disabling all monitoring and control plane functionality.

Quoted source text, attributed separately from HOL analysis.