# CVE-2026-111384: Nezha 1.0.0 before 2.3.15 Memory Exhaustion via File Manager WebSocket

> Authenticated users can cause a denial of service by sending oversized WebSocket messages to the file manager endpoint, crashing the monitoring dashboard.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-7242-982f-83p9, GHSA-ggj9-3h4w-qv8p

## What is CVE-2026-111384?

CVE-2026-111384 is a high-severity denial of service vulnerability in nezhahq nezha, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-111384?


## How do I fix CVE-2026-111384?

No fix has been published for CVE-2026-111384 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111384 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111384 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111384 and fix it if it is affected.

What it is: CVE-2026-111384 is a high-severity denial of service vulnerability in nezhahq nezha, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111384 exists.

Affected product: nezhahq nezha. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111384/ (Markdown: https://insights.sbomify.com/CVE-2026-111384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111384
- OSV: https://osv.dev/vulnerability/CVE-2026-111384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111384/
Summaries are generated and may contain mistakes; the official description above is the record.