Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-100394medium6.5

Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant

Impact

Nezha Monitoring versions 2.2.7 to 2.2.11 have a weakness that allows a RoleMember to crash the dashboard process, disrupting all tenants' access. This occurs due to a race condition and null pointer dereference. The issue affects availability only.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

nezhahq · GitHub_M

nezha

1 range
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 2.2.7, < 2.2.11

unaffected

unknown

Other versions: unknown

Original source description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From 2.2.7 until 2.2.11, ServiceSentinel.worker in service/singleton/servicesentinel.go checked an owned service under servicesLock and later dereferenced pointer-valued serviceStatusToday and serviceCurrentStatusData entries under serviceResponseDataStoreLock without revalidating that ServiceSentinel.Delete had not removed them. A RoleMember could concurrently report TCP or ICMP results through the member's own agent and delete the same owned service, causing a nil pointer dereference. Because the gRPC server had no recovery interceptor, the worker panic terminated the whole dashboard process and disrupted every tenant's web interface, REST API, and agent connections. The issue affects availability only and does not disclose or modify data. This issue is fixed in versions 2.2.11 and 2.3.0.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-100394

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

GitHub_M

Related →
CWE-476 ↗

CWE-476: NULL Pointer Dereference

GitHub_M

Related →
Contributing organizations · 2
GitHub_M

Assigning organization

2026-10-14
CISA-ADP

Additional data publisher

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

4 sources
github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9
exploitGitHub_M · CISA-ADP
github.com/nezhahq/nezha/commit/c893aa57867d8a3d608e2f2f16d1594c9766cdf3
PatchGitHub_M
github.com/nezhahq/nezha/releases/tag/v2.2.11
Release notesGitHub_M
github.com/nezhahq/nezha/releases/tag/v2.3.0
Release notesGitHub_M