CVE-2026-111383: Nezha resource exhaustion in WebSocket endpoint

CVE-2026-111383 · Severity: medium · CVSS 6.5 · Published 2026-10-16

Nezha is a server and network monitoring dashboard. An authenticated attacker can open thousands of concurrent WebSocket connections to the transfer endpoint without limits, exhausting memory, file descriptors, and goroutines. This causes the monitoring service to become unresponsive and unable to accept new agent connections, resulting in total loss of monitoring until the attack stops.

Technologies: Nezha. Vendors: Nezha.

Quick answers

Is CVE-2026-111383 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-111383 being exploited in the wild.
How severe is CVE-2026-111383?
Medium severity, with a CVSS score of 6.5, published 16 October 2026.
Which products and versions are affected?
Nezha 2.0.13 to 2.3.14.
Is there a fix for CVE-2026-111383?
Yes: fixed in 2.3.15. Until then: Restrict network access to the dashboard's HTTP(S) endpoint and limit authenticated user accounts to trusted administrators; implement firewall rules or a reverse proxy to rate-limit WebSocket connections per authenticated session. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111383 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-111383?
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.15

Restrict network access to the dashboard's HTTP(S) endpoint and limit authenticated user accounts to trusted administrators; implement firewall rules or a reverse proxy to rate-limit WebSocket connections per authenticated session.

Technical details

The /api/v1/ws/transfer WebSocket endpoint allows authenticated users to subscribe to server transfer events via ServerTransferClass.Subscribe() without enforcing per-user, per-IP, or global connection limits. Each subscription allocates a 72 KB buffered channel and spawns two goroutines, with no server-side idle timeout. An attacker can exhaust the dashboard process's file descriptor, memory, and goroutine capacity, blocking agent gRPC reconnections and causing service degradation or outage.

Affected products

  • Nezha Nezha 2.0.13 to 2.3.14

Timeline

  • 2026-10-01: disclosed
  • 2026-10-01: patched: Fix committed as 36b742a7
  • 2026-10-16: advisory

References

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