Skip to main content
VulnerabilityPublished Updated

CVE-2026-105113: nezhahq nezha · Improper Locking

Affects nezhahq nezhaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.3.13 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.13
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade nezha and nezhahq/nezha to 2.3.13.

Affected software

ProductAffectedFixed in
nezhahqnezhaAffected
  • >=1.8.0 <2.3.13
Fixed in
  • 2.3.13
GitHubnezhahq/nezhapkg:github/nezhahq/nezhaOther threatsAffected
  • >=1.8.0 <2.3.13
Fixed in
  • 2.3.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to authenticated non-admin users or monitor for abnormal alerting subsystem behavior to mitigate impact.

Description

Nezha Dashboard versions from 1.8.0 up to but not including 2.3.13 have an improper locking vulnerability. This flaw involves a non-deferred mutex unlock that leaks on a nil-map panic path. An authenticated non-admin user can exploit this by issuing four notification API calls, causing a permanent deadlock in the alerting subsystem and subsequently exhausting memory with blocking requests. The vulnerability has a CVSS 4.0 score of 7.1, indicating high severity.

References

Community reviews

Loading reviews…