Skip to main content
VulnerabilityPublished Updated

CVE-2026-100394: nezhahq nezha · Race Condition

Affects nezhahq nezhaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.11 when convenient.

Data as of 29 Oct 2026, 20:06 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.5
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 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 29 Oct 2026.

What to do

Upgrade nezha and github.com/nezhahq/nezha to 2.2.11.

Affected software

ProductAffectedFixed in
nezhahqnezhaAffected
  • >=2.2.7 <2.2.11
Fixed in
  • 2.2.11
Gogithub.com/nezhahq/nezhapkg:golang/github.com/nezhahq/nezhaOther threatsAffected
  • >=2.2.7 <2.2.11
Fixed in
  • 2.2.11

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

AI-suggested

Upgrade Nezha Monitoring to version 2.2.11 or later, where this race condition vulnerability is fixed. No other mitigation is required as the issue is resolved in these versions.

Description

A race condition vulnerability in Nezha Monitoring versions 2.2.7 through 2.2.10 allows a RoleMember to cause a nil pointer dereference in the ServiceSentinel worker. This leads to a panic that terminates the dashboard process, disrupting the web interface, REST API, and agent connections for all tenants. The issue affects availability only and does not expose or modify data. Fixed in version 2.2.11 and later.

References

Community reviews

Loading reviews…