Is CVE-2026-105112 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105112 being exploited in the wild.

How severe is CVE-2026-105112?

Medium severity, with a CVSS score of 5.3, published 3 October 2026.

Is there a fix for CVE-2026-105112?

Yes: fixed in 2.3.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-105112 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-105112?

Check whether you run Nezha at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105112: Nezha lock-order inversion in notification groups

CVE-2026-105112 · Severity: medium · CVSS 5.3 · Published 2026-10-03

Nezha is a dashboard and monitoring system for servers. A flaw in how its alerting subsystem manages access to notification groups allows authenticated non-administrator users to trigger a deadlock that permanently breaks alert delivery until the system restarts. An attacker with basic user credentials can cause critical notifications and monitoring alerts to fail silently with no warning.

Technologies: Nezha. Vendors: Nezha.

Quick answers

Is CVE-2026-105112 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105112 being exploited in the wild.
How severe is CVE-2026-105112?: Medium severity, with a CVSS score of 5.3, published 3 October 2026.
Which products and versions are affected?: Nezha 1.8.0 before 2.3.13.
Is there a fix for CVE-2026-105112?: Yes: fixed in 2.3.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105112 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-105112?: Check whether you run Nezha at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.3.13

Technical details

UpdateGroup and DeleteGroup functions in the notification subsystem acquire two mutexes (groupMu and listMu) in opposite orders, creating an ABBA deadlock cycle. An authenticated non-admin user can concurrently call the /api/v1/notification-group and /api/v1/batch-delete/notification-group endpoints with oversized ID lists to widen the race window and close the cycle. The deadlock permanently blocks all alert delivery, gRPC handlers, and notification CRUD operations until the process restarts.

Affected products

Nezha Nezha 1.8.0 before 2.3.13

Timeline

2026-09-19: disclosed
2026-10-03: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.