Quick answers
- Is CVE-2026-111384 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111384 being exploited in the wild.
- How severe is CVE-2026-111384?
- Medium severity, with a CVSS score of 6.5, published 16 October 2026.
- Which products and versions are affected?
- NezhaHQ Nezha 1.0.0 before 2.3.15.
- Is there a fix for CVE-2026-111384?
- Yes: fixed in 2.3.15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111384 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-111384?
- Check whether you run NezhaHQ 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
Technical details
The fmStream WebSocket handler in cmd/dashboard/controller/fm.go upgrades a connection without calling SetReadLimit, allowing gorilla/websocket to read an entire attacker-supplied message into memory unbounded. An authenticated user with server:read, server:write, and server:delete scopes can send a single binary WebSocket frame of arbitrary size to /api/v1/ws/file/:sessionID, triggering an out-of-memory kill. The parallel terminalStream endpoint has the same upgrade but correctly calls SetReadLimit(terminalWebSocketInputLimit), showing this is a missed security boundary.
Affected products
- nezhahq Nezha 1.0.0 before 2.3.15
Timeline
- 2026-10-01: patched: Fixed in commit 36b742a7
- 2026-10-01: advisory: GitHub Security Advisory GHSA-7242-982f-83p9 published
- 2026-10-16: disclosed