External risk intelligence

Kiloview E3 NDI Encoder Command Execution Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-109122

The vulnerability exists in the web management API of a network encoder appliance. Devices of this type are commonly deployed to manage and stream video content over networks, and their web-based administration interfaces are frequently exposed to management networks or directly to the internet to facilitate remote configuration and operation.

OS Command Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical security flaw has been identified in the Kiloview E3 NDI encoder firmware, specifically within its network management service. This issue allows an authenticated user to execute arbitrary commands on the device with root privileges, potentially leading to full system compromise and the exposure of sensitive information. The vulnerability's persistence across reboots heightens the risk.

  • Allows unauthorized command execution on network devices.
  • Could lead to full device compromise and data exposure.
  • Confirm relevance and assess exposure to critical systems.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access to the Kiloview E3 NDI encoder's web management API can exploit a flaw in how the system handles static route configurations. By providing specially crafted input to a field that is not properly sanitized, an attacker can inject and execute arbitrary operating system commands with root privileges. This malicious configuration is persistent, meaning it survives reboots, potentially leading to full device compromise.

  • Authenticated user access required.
  • Web API input field is not sanitized.
  • Full device compromise and credential theft.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user with permission to configure static routes could exploit this vulnerability to execute arbitrary operating system commands as root on the affected Kiloview E3 NDI encoder. This malicious configuration persists across reboots and could lead to full device compromise.

  • Device commands and credentials could be exposed.
  • An authenticated user could inject commands.
  • Full device compromise and data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world ownership of this vulnerability likely falls to teams managing network infrastructure and operational technology (OT) assets, such as infrastructure or platform teams, in conjunction with security operations. The first practical move is to identify all deployed Kiloview E3 NDI encoders, confirm their network accessibility, and determine their criticality to operations before planning remediation.

  • Network and OT teams should own the issue.
  • Verify affected device accessibility and criticality first.
  • Plan remediation based on confirmed risk exposure.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Kiloview E3 NDI encoder?

The Kiloview E3 is a hardware appliance designed to convert video signals into NDI (Network Device Interface) streams for professional broadcasting. It is widely used in live production environments to transport high-quality video over standard IP networks. The device includes a built-in network management service, accessed via a web-based API, that allows administrators to configure essential system functions, such as routing and network connectivity.

What does CVE-2026-109122 mean by command injection?

This vulnerability, classified as CWE-78 (OS Command Injection), occurs because the device fails to clean inputs provided in a static route configuration field. Because the system does not properly validate this text, it mistakenly treats malicious commands as legitimate instructions. Consequently, an attacker can force the underlying operating system to run unauthorized code with root-level privileges, giving them complete control over the device's functions.

How is this vulnerability triggered?

To trigger the flaw, an attacker must already have authenticated access to the device's web management API and possess the specific permissions required to modify static route configurations. Simply accessing the device’s landing page or viewing public streams without these credentials does not trigger the vulnerability. Once the malicious command is injected into the route configuration field, it becomes a permanent part of the system settings, surviving even after the device is rebooted.

Why should I care about this for my network?

According to Halo Surface Signal, these encoders are often managed via web interfaces that may be accessible from internal management networks or even directly from the internet for remote operations. Because this flaw allows for full system compromise, any device reachable by an unauthorized user poses a significant risk. If an attacker gains access to the management interface, they can extract stored credentials and cryptographic keys, effectively compromising the entire unit's security.

What is the first step for owners of these encoders?

If you manage these devices, start by creating a complete inventory of all deployed units in your environment. Evaluate how these devices are connected and determine if their web management interfaces are accessible over the network. Once you have identified the location and reachability of your encoders, prioritize them based on their importance to your operations while you prepare to apply the necessary firmware updates from the manufacturer.

References