CVE-2026-111384
Deferred Deferred - Pending Action

Memory Exhaustion in Nezha Dashboard File Manager

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: VulnCheck

Description
Nezha 1.0.0 before 2.3.15 contains a memory exhaustion vulnerability in the dashboard file manager WebSocket endpoint because fmStream never calls SetReadLimit, leaving message size unbounded. Authenticated users with file manager scopes can send one oversized binary message to /api/v1/ws/file/:id, triggering an OOM kill that drops all agent monitoring.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-111384
EUVD
EUVD-2026-102565

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nezhahq nezha 1.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Nezha 1.0.0 before 2.3.15 has a memory exhaustion vulnerability in the dashboard file manager WebSocket endpoint. The fmStream component does not set a read limit, allowing unbounded message sizes. Authenticated users with file manager scopes can send one oversized binary message to /api/v1/ws/file/:id, causing an OOM kill that disrupts all agent monitoring.

Detection Guidance

Monitor for unusually high memory usage on the Nezha dashboard server, particularly during WebSocket connections to /api/v1/ws/file/:id. Check logs for OOM kills or process crashes. Use network monitoring tools to detect large WebSocket messages from authenticated users with file manager permissions.

Impact Analysis

This vulnerability can cause system crashes due to out-of-memory conditions. A single 512 MB message can trigger an OOM kill on a 1 GiB VM, disabling monitoring until the process restarts. It requires authenticated access with file manager permissions.

Compliance Impact

This vulnerability can lead to denial-of-service conditions by exhausting server memory, disrupting monitoring services. For GDPR, this may impact availability of personal data processing systems, potentially violating Article 32 requirements for security and resilience. For HIPAA, it could disrupt monitoring of protected health information systems, affecting integrity and availability requirements under the Security Rule.

Mitigation Strategies

Upgrade Nezha to version 2.3.15 or later. If immediate upgrade is not possible, implement a reverse proxy with WebSocket size limits (e.g., Nginx client_max_body_size) to block oversized messages. Restrict file manager permissions to trusted users only.

Chat Assistant

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

EPSS Chart