# CVE-2026-101085: Nezha before 2.3.8 Denial of Service via Alert Rule

> Authenticated users can crash the Nezha dashboard by submitting malformed alert rules, causing persistent service outages.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-2qc6-x993-hjq9, GHSA-5j6x-8f94-88gc

## What is CVE-2026-101085?

CVE-2026-101085 is a high-severity denial of service vulnerability in nezhahq nezha, published on 27 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-197 (Numeric Truncation Error)

## Which versions are affected by CVE-2026-101085?


## How do I fix CVE-2026-101085?

No fix has been published for CVE-2026-101085 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101085 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101085 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101085 and fix it if it is affected.

What it is: CVE-2026-101085 is a high-severity denial of service vulnerability in nezhahq nezha, published on 27 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101085 exists.

Affected product: nezhahq nezha. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101085/ (Markdown: https://insights.sbomify.com/CVE-2026-101085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101085
- OSV: https://osv.dev/vulnerability/CVE-2026-101085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101085/
Summaries are generated and may contain mistakes; the official description above is the record.