Overview
On November 18, 2026, the Nginx team released fixes for five vulnerabilities that are collectively known as “Nginx to Root” (NGINX2Root): CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425. The most severe of these allows an unauthenticated remote attacker to execute commands on your server over HTTP/2, which is commonly enabled on sites served over HTTPS. The researchers who discovered the vulnerabilities also demonstrated that this remote code execution can be chained with a separate Linux kernel vulnerability to gain root access to the server.Affected Nginx versions
The HTTP/2 vulnerability has existed since Nginx introduced HTTP/2 support in version 1.9.5, released in 2015, so you should assume that every Forge server is vulnerable until it is patched.
The Linux kernel vulnerability used to escalate to root is tracked separately and requires its own kernel update. Patching Nginx closes the way in, but we recommend keeping automatic security updates enabled and rebooting your servers once the kernel patch is released.
Where Forge installs Nginx from
The package source depends on when your server was provisioned:
The
ondrej/nginx PPA has since been removed from Launchpad, so servers that still use it will not receive the fixed version. These servers must be switched to the official nginx.org repository before they can be patched, as described in Step 3.
Ubuntu 20.04 LTS and earlier
Servers running Ubuntu 20.04, 18.04, 16.04, or 14.04 cannot be patched. These Ubuntu versions have reached end of life, andnginx.org no longer builds packages for them. On Ubuntu 20.04, the newest available version is 1.27.5, which is still vulnerable.
We strongly recommend migrating your applications to a new server running Ubuntu 22.04 or later, ideally Ubuntu 26.04, or upgrading the operating system.
What you need to do
The following steps apply to servers running Ubuntu 22.04 LTS and later. Work through them in order.Step 1: Check your current Nginx version
SSH into your server, check the installed Nginx version, and check whether thenginx.org repository is already configured:
Step 2: Check where Nginx was installed from
Check the installed package version and its maintainer:NGINX Packaging <nginx-packaging@f5.com>, the package already comes from nginx.org, so you may skip to Step 4. If the output contains Ubuntu or sury.org (Ondřej Surý), continue with Step 3.
Step 3: Switch to the nginx.org repository
Run the following commands in order. Do not useadd-apt-repository --remove to remove the old PPA, as it fails now that Launchpad has removed the PPA.
Step 4: Install the update
Refresh the package lists and upgrade Nginx. The--only-upgrade flag ensures that no new packages are installed, and the --force-confold option keeps your existing Nginx configuration files:
Step 5: Verify the fix is active
Confirm that the new version is installed:listen ... http2 is deprecated warnings are harmless:
Notes and edge cases
- Removed modules: The Ondřej module packages (
brotli,geoip,image-filter,xslt, andssl-ct) are removed when switching tonginx.org. Thestreamandmailmodules are compiled into thenginx.orgbuilds. If Nginx does not start, remove theload_modulelines for any missing modules from/etc/nginx/nginx.confand/etc/nginx/modules-enabled. - Default server: The
nginx.orgpackage adds/etc/nginx/conf.d/default.conf. Check that your own default server still takes precedence. aptis locked: Another package operation is running. Wait a few minutes and try again.needrestartprompts: Accept the defaults. A reboot may be recommended if a new kernel was installed.