Skip to main content
Vulnerability Database/CVE-2026-105113

CVE-2026-105113: Nezha Dashboard Race Condition Vulnerability

CVE-2026-105113 is a race condition flaw in Nezha Dashboard that allows authenticated users to deadlock the alerting subsystem and exhaust memory. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-105113 Overview

CVE-2026-105113 is an improper locking vulnerability [CWE-667] in Nezha Dashboard versions 1.8.0 through 2.3.12. The flaw resides in the notification subsystem, where a non-deferred mutex unlock leaks on a nil-map panic path. Any authenticated non-admin member can issue four notification API calls to permanently deadlock the alerting subsystem. Follow-up blocking requests then exhaust server memory, causing a denial-of-service condition against the dashboard.

Critical Impact

Authenticated low-privilege users can permanently disable the Nezha alerting subsystem and exhaust server memory with a sequence of four notification API calls.

Affected Products

  • Nezha Dashboard 1.8.0 through 2.3.12
  • Nezha Dashboard deployments exposing notification APIs to authenticated members
  • Self-hosted Nezha monitoring instances prior to version 2.3.13

Discovery Timeline

  • 2026-10-03 - CVE-2026-105113 published to the National Vulnerability Database
  • 2026-10-05 - Last updated in NVD database

Technical Details for CVE-2026-105113

Vulnerability Analysis

The vulnerability stems from improper mutex handling in the notification code path of Nezha Dashboard. When the notification handler encounters an uninitialized map, it triggers a nil-map panic. Because the mutex unlock is not deferred, the panic unwinds the stack while the lock remains held. The alerting subsystem becomes permanently deadlocked after four notification API calls from any authenticated non-admin account. Subsequent requests that attempt to acquire the same mutex block indefinitely, accumulating goroutines and consuming memory until the process is terminated.

Root Cause

The root cause is a Go concurrency anti-pattern. The affected function acquires sync.Mutex without using defer mu.Unlock() before executing operations that can panic on a nil map. When the panic occurs, control transfers out of the function without releasing the mutex. This violates the contract described in [CWE-667: Improper Locking] and leaves the shared notification state inaccessible to any other goroutine.

Attack Vector

Exploitation requires only a low-privilege authenticated session. An attacker calls the notification endpoint four times to trigger the panic sequence and strand the mutex. After the deadlock is established, the attacker issues additional blocking notification requests. Each request spawns a goroutine that waits on the orphaned lock, which steadily inflates heap and goroutine memory until the dashboard process is killed by the operating system or becomes unresponsive.

No verified public exploit code is available. For technical specifics, see the GitHub Security Advisory GHSA-7j7v-j77m-6g3m and the VulnCheck Denial of Service Advisory.

Detection Methods for CVE-2026-105113

Indicators of Compromise

  • Repeated POST requests to Nezha notification API endpoints from a single authenticated non-admin account within a short window.
  • Sudden halt of alert delivery from the Nezha Dashboard despite active monitored agents.
  • Rapid, unbounded growth of resident memory and goroutine counts in the Nezha process.
  • Panic entries in Nezha logs referencing nil map access in the notification subsystem.

Detection Strategies

  • Monitor Nezha application logs for recurring nil map panic traces originating in notification handlers.
  • Correlate authenticated user activity against notification endpoint call frequency to flag abusive patterns.
  • Baseline normal alert delivery cadence and alarm on sustained silence from the notification pipeline.

Monitoring Recommendations

  • Track process-level memory, goroutine count, and file descriptor usage on hosts running Nezha Dashboard.
  • Enable HTTP access logging on the reverse proxy fronting Nezha and retain request-level metadata for notification routes.
  • Alert on authentication events from non-admin accounts followed by bursts of notification API traffic.

How to Mitigate CVE-2026-105113

Immediate Actions Required

  • Upgrade Nezha Dashboard to version 2.3.13 or later, which contains the official fix.
  • Audit non-admin member accounts and revoke any that are unused or untrusted.
  • Restrict network exposure of the dashboard to trusted administrative networks or a VPN.
  • Restart affected Nezha instances to clear deadlocked state after patching.

Patch Information

The Nezha maintainers released version 2.3.13 to address the improper locking defect. The fix ensures the notification mutex is released on all code paths, including panic recovery. Review the GitHub Security Advisory GHSA-7j7v-j77m-6g3m for upgrade guidance and commit references.

Workarounds

  • Temporarily disable member self-registration and limit account provisioning to administrators.
  • Place the dashboard behind a reverse proxy that rate-limits notification endpoints per authenticated session.
  • Monitor the Nezha process with a supervisor that restarts it when memory thresholds are exceeded.
bash
# Example NGINX rate limit for notification endpoints
limit_req_zone $binary_remote_addr zone=nezha_notify:10m rate=5r/m;

location /api/v1/notification {
    limit_req zone=nezha_notify burst=5 nodelay;
    proxy_pass http://nezha_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.