# CVE-2026-105113 — nezhahq nezha

> As of 2026-10-03, CVE-2026-105113 is a MEDIUM-severity vulnerability in nezhahq nezha, CVSS v3.1 6.5. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-105113 as of 2026-10-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-03

## What is CVE-2026-105113?

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.

The record classifies CVE-2026-105113 under weakness class [CWE-667](https://cwe.mitre.org/data/definitions/667.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 2 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.5 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **CVSS v4.0 base score:** 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`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-03

## Is CVE-2026-105113 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **nezhahq**: nezha

## How to fix CVE-2026-105113

No vendor patch reference has been recorded for CVE-2026-105113 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-105113

No threat campaign in the Threadlinqs corpus currently references CVE-2026-105113, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, GitHub Security Advisories. Last verified by Threadlinqs on 2026-10-04.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/nezhahq/nezha/security/advisories/GHSA-7j7v-j77m-6g3m)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/nezha-1.8.0-before-2.3.13-denial-of-service-via-notification-mutex-deadlock)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-105113
Full detection coverage and IOCs for threats exploiting CVE-2026-105113 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp