# CVE-2026-105113: Nezha 1.8.0 before 2.3.13 Denial of Service via Notification Mutex Deadlock

> Authenticated non-admin users can deadlock the alerting subsystem and exhaust memory via specific notification API calls in Nezha Dashboard.

- **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:** 3 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-2w9f-mhfg-hq53, GHSA-7j7v-j77m-6g3m

## What is CVE-2026-105113?

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

### Official description

Nezha Dashboard from 1.8.0 before 2.3.13 contains an improper locking vulnerability where a non-deferred mutex unlock leaks on a nil-map panic path. Any authenticated non-admin member can issue four notification API calls to permanently deadlock the alerting subsystem, then exhaust memory with blocking requests.

Weakness: CWE-667 (Improper Locking)

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


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

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

## Is CVE-2026-105113 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105113 is a high-severity denial of service vulnerability in nezhahq nezha, published on 3 Oct 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-105113 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-105113/ (Markdown: https://insights.sbomify.com/CVE-2026-105113/index.md)
```

## Sources

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

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