Remote execution through NGINX HTTP/2

TinyPilot Security Advisory #005

Published: November 20, 2026

Overview

TinyPilot Pro before 3.3.1 and TinyPilot Community releases before November 20, 2026 enable HTTP/2 in NGINX. Two vulnerabilities in NGINX can allow an unauthenticated attacker who can reach the device to run code on it.

What is the severity?

High.

Who is affected?

All users running TinyPilot Pro 3.3.0 or older, and all users running a TinyPilot Community release from before November 20, 2026.

The default configuration is affected, including devices that require HTTPS. An attacker does not need a TinyPilot username or password. The attacker does need a network path to the device, such as the local network, a VPN, or a port forward.

You can check which version of TinyPilot Pro your device runs by opening the TinyPilot web interface, navigating to the "Help" menu, and then clicking "About."

What is the impact?

An attacker who can open a connection to the device can run commands on it. From there, they can use the device's access to the target computer, including the screen, keyboard, mouse, and virtual media.

What can customers do?

TinyPilot Pro users should update to TinyPilot Pro 3.3.1 and then restart the device. TinyPilot Community users should update to the latest version and then restart the device. Restarting is required. Until the device restarts, an old NGINX process can keep the vulnerable behavior.

After updating, two MJPEG windows open in the same browser may both show video while the keyboard and mouse work in only one of them. H.264 video is unaffected.

How is TinyPilot addressing this issue?

TinyPilot Pro 3.3.1 disables HTTP/2 in NGINX, which removes the condition these vulnerabilities require. We applied the same change to TinyPilot Community in this update. A later release will install the patched NGINX package and turn HTTP/2 back on.

What are the technical details of the vulnerability?

The vulnerabilities are in NGINX, not in TinyPilot's application code. They are tracked as CVE-2026-123007 and CVE-2026-123633. Both require HTTP/2 to be enabled.

TinyPilot uses NGINX as its web server. TinyPilot's configuration turned HTTP/2 on for the ports NGINX serves, including the HTTPS port that browsers use. TinyPilot's login check runs after NGINX accepts the connection, so it does not prevent the attack.

Disabling HTTP/2 closes the vulnerable path. The NGINX package installed from the operating system remains vulnerable if HTTP/2 is turned back on before that package is upgraded.

Questions

If you have any questions or concerns about this issue, please contact our security team: