On November 18, 2026, the NGINX project disclosed five critical vulnerabilities and fixed them in NGINX 1.31.9 and 1.30.7. The researchers who found them call the set nginx2root. All five score 9.2 out of 10 on the Common Vulnerability Scoring System (CVSS) v4.0 scale, and none needs a login. Two are in HTTP/2, and CVE-2026-123634 is in the DNS resolver. InMotion Hosting began installing patched NGINX packages on the servers it manages that same day, so you do not need to patch those yourself. If you run your own NGINX on a Self-Managed VPS, Bare Metal server, or Docker, update now.
Note: This article is a snapshot as of November 20, 2026. Patch status changes as the rollout finishes, so check the InMotion Hosting status page for live notices. You are welcome to share this page with your own clients.
What We Know About nginx2root
What the NGINX advisories say
The NGINX security advisories page lists all five flaws. Each is a memory-safety bug that can crash a worker process or corrupt its memory. Code execution is possible where Address Space Layout Randomization (ASLR) is off or can be bypassed. All five carry the same CVSS score of 9.2. The NGINX project itself rates only two as major and three as medium.
| CVE | Component | What has to be enabled | NGINX project severity |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control | HTTP/2 | Major |
| CVE-2026-123633 | HTTP/2 | HTTP/2, proxying to a backend, and a worker low on worker_connections | Medium |
| CVE-2026-123634 | DNS resolver | A resolver, a proxy_pass with a variable, and a mirror or SSI subrequest | Medium |
| CVE-2026-121810 | HTTP/3 (QUIC) | HTTP/3 and a worker low on worker_connections | Medium |
| CVE-2026-113425 | Mail proxy | NGINX used as a mail proxy | Major |
What the researchers report
The name comes from Xint, the researchers who found the bugs. Xint says any one of the five can be chained with a separate Linux kernel flaw in the Stream Control Transmission Protocol (SCTP) to reach root. That kernel bug had no CVE and no patch as of November 18. Xint also reports that the chain escaped a Docker container in its tests. Whether that works depends on the kernel and the container’s restrictions.
A public exploit exists for CVE-2026-123007 only. Rapid7 published it. It needs roughly 128 GB of HTTP/2 traffic and a way around ASLR. No attacks in the wild had been reported as of November 18.
About CVE-2026-123634
CVE-2026-123634 is a use-after-free in the NGINX resolver, the part that looks up domain names while a request runs. Two requests waiting on the same lookup can leave NGINX using memory it already released. That can crash a worker or, in the worst case, run an attacker’s code.
It needs three things at once: a resolver directive, a proxy_pass with a variable in the server name, and a mirror or Server Side Includes (SSI) subrequest resolving the same name. Turning off HTTP/2 does not fix it, and neither does turning off mirror alone. Until you patch, point proxy_pass at a fixed upstream group so there are no lookups at request time.
Which InMotion Hosting Servers Run NGINX
- WordPress Hosting: NGINX runs as a reverse-proxy cache in front of Apache.
- Managed VPS and Managed Dedicated with UltraStack: These servers use the same design, managed through the NGINX Cache Manager. See Advanced NGINX on VPS and Dedicated.
- Shared: Some Shared servers run NGINX, and InMotion Hosting manages it.
- cPanel servers: They can run cPanel’s optional “NGINX with Reverse Proxy” (
ea-nginx). See how to install NGINX on cPanel. - Self-Managed VPS, Bare Metal, and Docker Ready VPS: These servers run whatever NGINX you installed, and you are responsible for updating it.
What InMotion Hosting Is Doing About nginx2root
InMotion Hosting began installing patched NGINX packages on November 18, 2026, starting with the Shared servers that run NGINX. Dedicated servers and VPS host nodes followed, and the rollout continued overnight. On November 19, InMotion Hosting updated every UltraStack ONE VPS to NGINX 1.30.7 from inside each VPS. The new binary was swapped in without dropping connections, and InMotion Hosting rebuilt its own NGINX modules to match. The update covers three packages: imh-nginx (InMotion Hosting’s own NGINX build for UltraStack servers), the operating system nginx package, and cPanel’s ea-nginx.
Deployment status as of November 20, 2026: InMotion Hosting’s systems team has marked nginx2root as patched on UltraStack Shared, VPS, and Dedicated servers. Where a patched NGINX package was not yet available, the team disabled HTTP/2 on that server as an interim step, which closes the two HTTP/2 flaws, and will install the package as soon as the vendor ships it. InMotion Hosting will update this article when those servers receive the package.
What You Should Do About nginx2root
Shared, WordPress Hosting, Managed VPS, and Managed Dedicated: InMotion Hosting has applied the NGINX update or the interim HTTP/2 mitigation across its managed servers, so you do not need to run it yourself. To confirm your server’s status, open a ticket or start a chat through AMP. Technical Support or Advanced Product Support answers patch questions. If you installed a separate NGINX of your own on a managed server, follow the self-managed steps later in this section for that copy.
Self-Managed VPS, Bare Metal, and Docker Ready VPS: Update now. On AlmaLinux, refresh the package metadata, then upgrade NGINX:
sudo dnf clean metadatasudo dnf upgrade 'nginx*'AlmaLinux 8’s default NGINX stream (1.14) is retired and gets no fix, so switch to a supported stream. Disabling HTTP/2 in the meantime covers only the two HTTP/2 CVEs. The AlmaLinux announcement lists the patched package versions. Confirm that yours is at or above them. On Ubuntu, USN-9159-1 fixes eight of the CVEs in this release, including all five nginx2root CVEs on the Ubuntu releases they affect.
sudo apt update && sudo apt upgrade nginxThen restart NGINX on either system. A reload does not replace the running program. The basic NGINX commands article covers the rest.
sudo systemctl restart nginxOn Docker, pull the 1.30.7 or 1.31.9 image and redeploy. Running containers stay vulnerable until you do. Some systems had no fix yet: Red Hat Enterprise Linux (RHEL) as of November 18, and Debian 12 and 13 as of November 19. On those systems, disable HTTP/2 as an interim step and watch the vendor for updates. That covers only the two HTTP/2 CVEs.
How to check your version: nginx -v can mislead on distribution builds, because backported fixes keep the old version number. Check the package instead. On AlmaLinux:
rpm -q nginxOn Ubuntu or Debian:
dpkg -l nginxTo confirm the patched program is the one running, list the running binary. A “(deleted)” suffix means the old binary is still in memory and NGINX needs a restart.
sudo ls -l /proc/$(cat /run/nginx.pid)/exeSelf-managed cPanel servers with NGINX (ea-nginx): cPanel has updated its ea-nginx source code to NGINX 1.31.9. That build includes every nginx2root fix except CVE-2026-121810, because ea-nginx is not built with HTTP/3. As of November 19, cPanel’s EasyApache 4 change log did not yet list it. Once it reaches the repository, run the normal update:
sudo dnf upgrade ea-nginxThen check the result with rpm -q ea-nginx. cPanel’s documentation says you must install the ea-nginx-http2 package to use HTTP/2 with ea-nginx, so the two HTTP/2 CVEs apply only if that package is installed.
What Comes Next
InMotion Hosting will update this article when the kernel SCTP bug gets a CVE and a patch, when cPanel’s change log lists ea-nginx 1.31.9, and when the managed servers on the interim HTTP/2 mitigation receive the patched package. The status page carries live notices. For the full vendor details, see the NGINX security advisories and the NGINX changelog.