CVE-2026-111384: nezhahq nezha · Unthrottled Resource Allocation
Affects nezhahq nezhaSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 2.3.15 soon.
Data as of 18 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.5 |
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.15
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade nezhahq nezha to 2.3.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nezhahqnezha | Affected
| Fixed in
|
Gonezhapkg:golang/nezhaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability affects Nezha versions prior to 2.3.15. Users should upgrade to version 2.3.15 or later where this issue is fixed. Patch status is not explicitly stated in the input data, but the version range indicates the fix was introduced in 2.3.15. Until upgraded, restrict file manager scope access to trusted users to reduce risk.
Description
Nezha versions 1.0.0 up to but not including 2.3.15 have a memory exhaustion vulnerability in the dashboard file manager WebSocket endpoint. This occurs because the fmStream component does not set a read limit on incoming messages, allowing authenticated users with file manager permissions to send an oversized binary message. Exploiting this can cause an out-of-memory (OOM) kill, which disrupts agent monitoring.