Zero Radar
← feed
CriticalVulnerabilityCVE-2026-109122updated 25 Oct 2026, 17:05 UTC

Kiloview E3 NDI encoder lets logged-in users run commands as root

A user with access to the device's web settings can plant a command that runs with full control of the device, and it keeps running after restarts. An attacker could then take over the encoder and read stored passwords and keys.

Official, 2 sources
SeverityCriticalCVSS 9.4 of 10
Being exploited?UnclearNo reports either way yet
Fix available?UnclearNo fixed version published in the sources yet
How sure is this?Official, 2 sourcesBacked by an official source

How the attack works simplified

  1. 1Authenticated userHas static-route configuration permission
  2. 2Web management APIStatic route field sent without sanitizing
  3. 3Network serviceInjected OS command executes
  4. 4Persistent root commandSaved config re-runs after reboot
  5. 5Credentials exposedStored secrets and crypto material readable
  6. ResultAttacker gains full root control of device

What happened

The network management service in Kiloview E3 NDI encoder firmware does not sanitize one field used when configuring static routes through the web management API, enabling OS command injection as root by an authenticated user with static-route permission.

Why it is dangerous: Successful exploitation gives full device compromise, including exposure of stored credentials and cryptographic material, and the malicious setting survives reboots. Sites running these encoders on shared or poorly segmented networks are most at risk.

Are you affected?

You are affected if you run Kiloview E3 NDI encoder firmware with the web management interface enabled and users who can configure static routes.

Kiloview E3 NDI encoder firmware (affected versions not specified in the provided material)

What to do

  1. Check with Kiloview or your vendor for a firmware update that fixes this issue and install it as soon as it is available
  2. Restrict access to the encoder's web management interface to trusted administrators on a separate management network
  3. Review which accounts have permission to configure static routes and remove any that are not needed
  4. Check existing static route settings for unexpected or unfamiliar entries and rotate any credentials stored on the device if you find signs of tampering

Timeline

  1. 22 Oct 2026, 22:17 UTC
    Publicly disclosed
  2. 22 Oct 2026, 22:17 UTC
    Reported by NVD · NVD
  3. 25 Oct 2026, 17:05 UTC
    GitHub Advisory reported on it · GitHub Advisory

Sources 2 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-109122 · GHSA-f5fq-95vg-f6g7
CVSS
9.4 / 10
EPSS
0.5% chance of exploitation within 30 days
Disclosed
22 Oct 2026, 22:17 UTC
On Zero Radar
before the radar started
Last change
25 Oct 2026, 17:05 UTC

The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works

Kiloview E3 NDI encoder lets logged-in users run commands as root · Zero Radar