Nezha from 1.8.0 before 2.3.13 contains a lock-order inversion in UpdateGroup and DeleteGroup that allows authenticated non-admin users to deadlock the alerting subsystem. Attackers can concurrently call the notification-group and batch-delete endpoints with oversized id lists to widen the race and close an ABBA cycle, permanently killing alert delivery until restart.
References
Configurations
No configuration.
History
05 Oct 2026, 16:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/nezhahq/nezha/security/advisories/GHSA-53vr-p24v-qvwf - |
03 Oct 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-03 14:16
Updated : 2026-10-05 16:17
NVD link : CVE-2026-105112
Mitre link : CVE-2026-105112
CVE.ORG link : CVE-2026-105112
JSON object : View
Products Affected
No product.
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
