CVE-2026-105112
Received Received - Intake

Nezha Alerting Subsystem Deadlock via Lock-Order Inversion

Publication date: 2026-10-03

Last updated on: 2026-10-03

Assigner: VulnCheck

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-03
Last Modified
2026-10-03
Generated
2026-10-03
AI Q&A
2026-10-03
EPSS Evaluated
N/A
NVD
CVE-2026-105112
EUVD
EUVD-2026-92016

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nezha nezha From 1.8.0 (inc) to 2.3.13 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a lock-order inversion vulnerability in Nezha versions 1.8.0 to 2.3.12. It involves two functions, UpdateGroup and DeleteGroup, that acquire the same two mutexes in opposite orders, creating an ABBA deadlock scenario. Authenticated non-admin users can exploit this by concurrently calling notification-group and batch-delete endpoints with large ID lists, causing a permanent deadlock in the alerting subsystem.

Detection Guidance

Monitor for deadlocks in the Nezha alerting subsystem by checking for unresponsive alert delivery or cron-failure notifications. Look for goroutines stuck in mutex acquisition in logs or via debugging tools like pprof. High CPU usage with no alert activity may indicate exploitation.

Impact Analysis

The vulnerability allows attackers to permanently disable all alerting, cron-failure notifications, and critical functions for all tenants. The system remains active but logs nothing, and alert delivery stops until a restart. This can lead to missed critical alerts and system failures.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by disrupting critical alerting systems that are required for monitoring and reporting security incidents. A deadlock in the alerting subsystem may prevent timely detection and response to breaches or failures, violating obligations for incident reporting under GDPR and HIPAA.

Mitigation Strategies

Upgrade Nezha to version 2.3.13 or later to patch the lock-order inversion. If immediate upgrade is not possible, restrict non-admin user access to notification-group and batch-delete endpoints until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105112. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart