CVE-2026-100394

CVSS 6.5 (medium) · published 2026-10-14

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.

Weakness: CWE-362, CWE-476

Source: NVD CVE-2026-100394

References

• https://github.com/nezhahq/nezha/commit/c893aa57867d8a3d608e2f2f16d1594c9766cdf3
• https://github.com/nezhahq/nezha/releases/tag/v2.2.11
• https://github.com/nezhahq/nezha/releases/tag/v2.3.0
• https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9
• https://github.com/nezhahq/nezha/security/advisories/GHSA-qjpp-gffx-2wm9

Check your software

Connect an AI agent to the FixLane MCP server or ask the Telegram bot to check what you have installed against incidents with a verified fixed version.