Skip to content
NGINX2Root: Clever Cloud runtimes don't enable the affected features (Security update)

NGINX2Root: Clever Cloud runtimes don't enable the affected features (Security update)

November 19, 2026·David Legrand
David Legrand

The NGINX security advisories describe five vulnerabilities fixed in NGINX 1.30.7 and 1.31.9, known as NGINX2Root. Some of them can allow unauthenticated remote code execution with the privileges of the NGINX worker process. Each one requires a specific feature to be enabled:

Clever Cloud runtimes

Python and Ruby runtimes use NGINX in front of your application. Their configuration enables none of these features: you have nothing to do. We will nevertheless update NGINX in our images shortly to 1.30.7, the latest stable release, which includes these fixes.

The custom services we provide to some customers that could be affected have all been updated already.

Your own NGINX

If you run your own NGINX, in a Docker or Linux application for example, our load balancers forward requests to it in HTTP/1.1: an attacker can’t reach the HTTP/2 and HTTP/3 vulnerabilities through them. Your application can still be exposed if its configuration combines resolver, a proxy_pass destination built from the request and mirror, or if a TCP redirection gives direct access to NGINX.

Update it to 1.30.7 or 1.31.9 anyway. Until then, disable the affected features you don’t need, as described in the researchers’ write-up.

If you have any questions or need help, contact Clever Cloud support.

Last updated on