CVE-2026-101088 Nezha before 2.3.1 Denial of Service via Concurrent Server Delete
An authenticated user can trigger a race condition during concurrent server deletion, causing an unrecovered panic that crashes the monitoring service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-101088?
CVE-2026-101088 is a medium-severity vulnerability in nezhahq nezha, published on 27 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Nezha is a server and website monitoring tool. In versions >= 2.2.11 and < 2.3.1, the service sentinel worker (service/singleton/servicesentinel.go) contains an incomplete fix for a previously reported nil dereference denial of service (GHSA-qjpp-gffx-2wm9). The 2026-07-21 fix re-validated the service lifecycle under serviceResponseDataStoreLock but reused an already-captured, now stale reporter pointer and never re-validated the server, and that lock does not guard ServerShared. An authenticated user with the member role who owns an agent can issue a concurrent server delete (POST /api/v1/batch-delete/server) for their own server to win the race window, causing the worker to dereference a missing entry in the server list snapshot. Because the sentinel workers and the gRPC server have no recover()/recovery interceptor, the resulting panic is unrecovered and crashes the entire instance. This is fixed in version 2.3.1.
Weakness: CWE-367
Which versions are affected by CVE-2026-101088?
How do I fix CVE-2026-101088?
No fix has been published for CVE-2026-101088 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-101088 being exploited?
There is no known exploitation of CVE-2026-101088 in the wild and no public exploit code.
Sources
Also known as GHSA-fqx6-jcw7-6879, GHSA-jx78-55p5-rwv5.