TL;DR: last updated 2026-11-19 13:50 UTC
nginx2root is Xint’s name for five flaws in nginx, disclosed on November 18, 2026. F5, which maintains nginx, rates all five 9.2 (Critical) on CVSS 4.0. The most widely reachable, CVE-2026-123007, needs only HTTP/2 turned on. Crafted traffic can crash nginx worker processes and, in some configurations, run code with a worker’s privileges.
yum update nginx and restart nginx, then check rpm -q nginx against the table. The fixes are backported, so nginx -v still shows the old version number. On CloudLinux 9 with nginx 1.26, the fix needs CloudLinux 9.9, which is still rolling out: see System nginx: fixed builds.rpm -q nginx shows a build older than the one in the table, update again.yum update ea-nginx, which also restarts nginx. The fixed build is ea-nginx-1.31.9-1~urgent or later. See cPanel servers: ea-nginx.nginx 1.30.7 and 1.31.9, released on November 18, fix the five nginx2root flaws, which the Xint research team found and reported to F5 in October. The fixes are backported into every system nginx build CloudLinux ships, and ea-nginx moves to nginx 1.31.9. What to do on a CloudLinux server depends on which nginx it runs.
On CloudLinux 7 to 10:
rpm -q nginx ea-nginx
The nginx package is the system nginx, the one that comes with the operating system. ea-nginx is nginx on cPanel servers. For a package that isn’t installed, it prints package ea-nginx is not installed (or package nginx is not installed). If nginx runs on the server but neither package is installed, it was installed some other way, and its fix comes from whoever built it.
On CloudLinux for Ubuntu 22.04, the system nginx is Ubuntu’s own package, which Ubuntu updates.
The system nginx is nginx 1.14 to 1.26, depending on the CloudLinux version and the module stream in use, and every one of them is affected. Each row lists the first build that carries every fix that applies to it.
| CloudLinux version | nginx version | Fixed in |
|---|---|---|
| CloudLinux 7 (ELS) | 1.20 | nginx-1.20.1-10.el7.tuxcare.els17 |
| CloudLinux 8 | 1.14 (default) | nginx-1.14.1-9.module_el8.10.0+7343+af250afe.cloudlinux.4 |
| CloudLinux 8 | 1.16 | nginx-1.16.1-2.module_el8.10.0+7344+68135136.1.cloudlinux.4 |
| CloudLinux 8 | 1.18 | nginx-1.18.0-3.module_el8.10.0+7345+f736ed63.1.cloudlinux.4 |
| CloudLinux 8 | 1.20 | nginx-1.20.1-1.module_el8.10.0+7346+9bd89172.1.cloudlinux.3 |
| CloudLinux 8 | 1.22 | nginx-1.22.1-1.module_el8.10.0+7347+6d9c8a63.1.cloudlinux.3 |
| CloudLinux 8 | 1.24 | nginx-1.24.0-3.module_el8.10.0+7348+69171071.6.cloudlinux.3 |
| CloudLinux 9 | 1.20 (default) | nginx-1.20.1-32.el9_9.1.cloudlinux.3 |
| CloudLinux 9 | 1.22 | nginx-1.22.1-8.module_el9.9.0+439+b175c265.1.cloudlinux.4 |
| CloudLinux 9 | 1.24 | nginx-1.24.0-9.module_el9.9.0+440+16ab46e3.1.cloudlinux.3 |
| CloudLinux 9 | 1.26 | nginx-1.26.3-10.module_el9.9.0+357+ccfac862.1.alma.2, on CloudLinux 9.9 (see the update below) |
| CloudLinux 10 | 1.26 (default) | nginx-1.26.3-16.el10_3.1.alma.3 |
CVE-2026-123633 affects nginx 1.19.7 and later, and CVE-2026-121810 nginx 1.25.0 and later, so the builds for older versions don’t need those fixes.
On CloudLinux 9 with nginx 1.26 and on CloudLinux 10, CloudLinux ships AlmaLinux’s build unchanged, which is why those build names end in alma.
Update: 2026-11-19 13:50 UTC.
On CloudLinux 9 with nginx 1.26, the fixed build is AlmaLinux’s build for CloudLinux 9.9, and CloudLinux 9.9 is still rolling out to servers on 9.8. Until it reaches a server, yum update nginx finds nothing there. To get the fix now, move the server to CloudLinux 9.9 through the rollout bypass repository, as in the CloudLinux 9.9 release post, then restart nginx:
dnf --enablerepo=cloudlinux-rollout-8-bypass install cloudlinux-release
dnf update
systemctl restart nginx
If you can’t move to 9.9 yet, turn HTTP/2 and HTTP/3 off until the rollout reaches the server (see Is your server exposed?).
The fixed builds are in the stable repositories.
yum update nginx
systemctl restart nginx
nginx keeps running the old code until it restarts. A configuration reload isn’t enough. If yum reports nothing to do and rpm -q nginx shows a build older than the one in the table, the server’s mirror hasn’t synced the fix yet. Try again later.
rpm -q nginx
The version at the start of the build tells you which row applies, and the build should be the one in that row or later. nginx -v doesn’t tell you, because the fixes are backported and the version number stays the same.
On cPanel servers, nginx comes as ea-nginx, which CloudLinux builds for cPanel servers on CloudLinux 7, 8, 9, and 10 and on CloudLinux for Ubuntu 22.04. The fixed build moves ea-nginx to nginx 1.31.9 and has been in the stable repositories since November 18.
On CloudLinux 7 to 10:
yum update ea-nginx
rpm -q ea-nginx
The update restarts nginx. It also updates any ea-nginx modules on the server, such as MAx Cache or mod_lsapi for nginx, to their builds for nginx 1.31.9.
The version should be 1.31.9-1~urgent or later.
Until you can update, the configuration decides which flaws can reach a server.
HTTP/2 is off by default in every nginx package CloudLinux ships. The system nginx’s default configuration listens on port 80 only, with the HTTPS and HTTP/2 settings commented out, so it serves HTTP/2 only where an administrator turned it on. On cPanel servers, ea-nginx turns HTTP/2 on for every SSL site when the optional ea-nginx-http2 package is installed. To check on CloudLinux 7 to 10:
rpm -q ea-nginx-http2
Turning HTTP/2 off blocks CVE-2026-123007 and CVE-2026-123633. The other three flaws need other features, listed in About the flaws.
For servers that can’t update yet, Xint’s write-up has commands that check each condition, including whether HTTP/2 is reachable from the internet (section 2.3), and a mitigation for each flaw (section 3.3).
The five flaws are independent, and each needs its own nginx configuration to be reachable.
| CVE | Where it is | What a server needs to be exposed |
|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control: a heap buffer overflow | HTTP/2 turned on |
| CVE-2026-123633 | HTTP/2: a use-after-free | HTTP/2 with requests passed to a backend server (nginx 1.19.7 and later) |
| CVE-2026-123634 | The resolver: a use-after-free | resolver, a proxy_pass destination built from the request, and subrequests, for example from mirror |
| CVE-2026-121810 | HTTP/3: a use-after-free | HTTP/3 with requests passed to a backend server (nginx 1.25.0 and later) |
| CVE-2026-113425 | The mail proxy: a use-after-free | nginx used as a mail proxy with auth_http |
F5 scores each of the five 8.1 (High) on CVSS 3.1 and 9.2 (Critical) on CVSS 4.0. For CVE-2026-123007, F5 says crafted HTTP/2 traffic can crash an nginx worker, and code execution is possible where address space layout randomization (ASLR) is off or the attacker can get around it.
Xint says each of the five can lead to remote code execution on its own, without authentication, with the privileges of the nginx worker process that handles the request. Worker processes normally run with restricted permissions, so full control of a server takes a second flaw. Xint chained one of the nginx flaws with a Linux kernel flaw to get root, and in its tests the chain also worked when nginx ran in a container, giving root on the host. Xint is withholding the kernel flaw’s details until a kernel fix is available.
As of November 18, CISA’s assessment in the CVE record lists exploitation as none. Xint has published demonstration videos but left out the final steps needed to reproduce its exploits.
Akos Vajda
Comments