Netdata: WebSocket Decompression Bomb

Answer in brief

CVE-2026-83599 records a High severity (CVSS 7.5) vulnerability in Netdata: WebSocket Decompression Bomb. The current sources do not mark it as known exploited. The current feed maps netdata/netdata (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 22, 2026Updated Sep 22, 2026Source checked Sep 22, 2026First seen by HOL Sep 22, 2026Material review Sep 22, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps netdata/netdata (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
netdata/netdatageneric	<2.11.0	2.11.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for netdata/netdata.
Review the reported fix. Update netdata/netdata to 2.11.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 22, 2026

Sources and claim methodology

Upstream source description

Netdata is an open source observability tool. Prior to 2.11.0, Netdata's unauthenticated WebSocket server negotiates permessage-deflate before authentication, and src/web/websocket/websocket-compression.c allows websocket_client_decompress_message() to grow decompressed output toward WS_MAX_DECOMPRESSED_SIZE without enforcing a compressed-to-decompressed ratio. Small highly compressed frames can therefore cause large server-side allocations, and repeated concurrent connections can exhaust memory and terminate monitoring. This vulnerability is fixed in 2.11.0.

Quoted source text, attributed separately from HOL analysis.