Skip to main content
VulnerabilityPublished Updated

CVE-2026-105112: nezhahq nezha · Race Condition

Affects nezhahq nezhaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 2.3.13 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% 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:H/AT:P/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 16 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 the notification-group and batch-delete endpoints to trusted users only and monitor for unusual concurrent calls that could trigger the deadlock.

Description

Nezha versions from 1.8.0 up to but not including 2.3.13 contain a race condition due to a lock-order inversion in the UpdateGroup and DeleteGroup functions. This flaw allows authenticated non-admin users to cause a deadlock in the alerting subsystem by concurrently invoking notification-group and batch-delete endpoints with oversized ID lists. The deadlock can permanently disrupt alert delivery until the system is restarted.

References

Community reviews

Loading reviews…