# CVE-2026-83600: Netdata: Streaming protocol chart slot guard off-by-one allows ~16 GiB allocation request, crashing parent agent

> An authenticated child agent can trigger a massive memory allocation in the parent Netdata agent, causing a crash and disabling centralized monitoring.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-83600, GHSA-3mxw-fv2x-rhc6, MINI-7gc7-3v6v-6j59, MINI-xmch-g7gq-hrcp, UBUNTU-CVE-2026-83600

## What is CVE-2026-83600?

CVE-2026-83600 is a medium-severity denial of service vulnerability in netdata, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Netdata is an open source observability tool. Prior to 2.10.4, an authenticated child agent can send an oversized CHART SLOT value that str2ull_encoded passes to pluginsd_rrdset_cache_put_to_slot in src/plugins.d/pluginsd_internals.h. The accepted slot drives reallocz to request an approximately 16 GiB chart-pointer array, and allocation failure invokes fatal and aborts the parent Netdata agent, repeatedly disabling centralized monitoring while stream access persists. This issue is fixed in version 2.10.4 and nightly build 2.10.0-782-nightly.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-193 (Off-by-one Error)

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


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

Upgrade to a fixed version.

## Is CVE-2026-83600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-83600 is a medium-severity denial of service vulnerability in netdata, published on 22 Sep 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-83600 exists.

Affected product: netdata. 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-83600/ (Markdown: https://insights.sbomify.com/CVE-2026-83600/index.md)
```

## Sources

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

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