Content Error or Suggest an Edit
Notice a grammatical error or technical inaccuracy? Let us know; we will give you credit!
Introduction
⚡ Short on time? The key facts and fixes are in the TL;DR.
On November 18, 2026, Xint disclosed nginx2root: five separate nginx vulnerabilities that each let an unauthenticated attacker run commands as the nginx worker user, plus a Linux kernel SCTP flaw that turns that foothold into root. The worst of the five, CVE-2026-123007, needs nothing more than HTTP/2 being enabled and reachable. It affects every nginx release from 1.9.5 (2015) through 1.31.8.
If you run WordPress on nginx (GridPane, RunCloud, a Docker stack, or your own Ubuntu box), you are almost certainly in scope. HTTP/2 is on by default on nearly every WordPress stack. The fix is nginx 1.31.9 (mainline) or 1.30.7 (stable). Your job today is to find out when your panel or distro ships it, and to restart nginx once it lands.
TL;DR
- What: Five nginx RCE CVEs (CVE-2026-123007, -123634, -123633, -121810, -113425). F5 scores each one 9.2 under CVSS 4.0. The HTTP/2 bug hits standard WordPress configs.
- Fix: nginx 1.31.9 or 1.30.7, or your vendor’s backported package, then a full restart. A reload doesn’t replace the running binary.
- Can’t patch yet: Turning off HTTP/2 blocks the two HTTP/2 bugs. If your origin is only reachable through Cloudflare’s proxy, Cloudflare says that covers you while you update.
- Kernel: The SCTP root-escalation bug has no CVE and no patch yet. Block the
sctpmodule on hosts that don’t need it. - Check: Don’t trust
nginx -valone. Distros backport fixes, so check the package against your distro’s advisory. - Status: No in-the-wild exploitation reported and not on CISA KEV as of the evening of November 18. Rapid7 has published a public proof of concept for CVE-2026-123007, so expect that to change quickly.
How It Works
Xint’s write-up describes five independent memory-safety bugs in different nginx modules:
- CVE-2026-123007: HTTP/2 enabled (1.9.5 and later). The big one.
- CVE-2026-123633: HTTP/2 with requests proxied to an upstream (1.19.7 and later).
- CVE-2026-123634:
resolverwith a request-derivedproxy_passandmirror(1.13.4 and later). - CVE-2026-121810: HTTP/3/QUIC with requests proxied to an upstream (1.25.0 and later).
- CVE-2026-113425: Mail proxy with
proxy onandauth_http(0.5.15 and later).
Each one gives code execution as the nginx worker, which is usually www-data, nginx or a panel-specific user, not root. The “2root” part comes from a sixth bug: a use-after-free in the Linux kernel’s SCTP send path, present since kernel 4.15 (2018). Chained with any of the nginx bugs, it gets the attacker root on the host. Aikido reports that this works even from inside a Docker container. We haven’t seen the technical basis for that claim, so treat it as unconfirmed.
Precursor notes that the main HTTP/2 attack doesn’t show up as normal logged requests. That is also why Cloudflare says it has no WAF rule for it. Don’t count on a request-inspecting WAF to save you.
What We Know So Far
- Oct 11, 2026: Xint found the bugs. They reported them to F5 through HackerOne on Oct 16.
- Nov 10: The nginx team asked Xint to validate the patches.
- Nov 18: Public disclosure, coordinated with F5, AWS, Azure and GCP. nginx 1.31.9 and 1.30.7 were released, and the Docker official images were updated that afternoon.
- Exploit code: Rapid7 has published a proof of concept for CVE-2026-123007. Xint and Wiz say they won’t release theirs. Fake “exploit” repositories are already circulating, so don’t run them.
- Exploitation: None reported in the wild yet. Not on CISA KEV yet.
This is nginx’s ninth security release of 2026. If you read our NGINX Rift post in May, that bug was exploited within days of disclosure. Plan for the same here.
Affected Versions and Exposure
| Version | |
|---|---|
| Affected (CVE-2026-123007) | 1.9.5 – 1.31.8 |
| Fixed, mainline | 1.31.9 |
| Fixed, stable | 1.30.7 |
| NGINX Plus | 37.3.0.1 / 37.0.8.1 (R34–R36: no fix, move to 37.x) |
| ingress-nginx | No patch planned, per Aikido; disable HTTP/2 or migrate |
Distro packages are behind as of writing. Ubuntu marks nginx as “needed” on 20.04, 22.04 and 24.04. Red Hat lists RHEL 8, 9 and 10 as “Under investigation”. Debian hadn’t published tracker entries yet. Distros backport fixes, so a patched Ubuntu box may still report 1.18.0 or 1.24.0.
You’re exposed if nginx serves HTTP/2 directly to the internet, which is the default on most WordPress stacks. Only CVE-2026-123007 is near-universal. The other four need the specific features listed above.
WordPress Hosting Providers and Control Panels
Every nginx-based panel ships its own build or uses the distro package, so the patch comes from your vendor. None of the providers below had published a statement when we checked on November 18.
| Platform | How nginx is shipped | Exposure |
|---|---|---|
| GridPane | Custom nginx build, HTTP/2 on | Affected until GridPane ships 1.31.9/1.30.7 |
| RunCloud (native) | nginx-rc package | Affected until RunCloud ships an update |
| RunCloud (Docker) | runcloud/nginx-rc image | Separate check: image needs rebuilding |
| Enhance | Containerized web servers (nginx or OLS) | Ask, especially for container and kernel exposure |
| FlyWP | Docker, nginx-based | Ask; image update needed |
| cPanel/WHM, Plesk, DirectAdmin | Mostly Apache/LiteSpeed; nginx optional as a proxy | Affected only if nginx is enabled |
| CloudPanel, HestiaCP | nginx | Affected until the distro/panel package updates |
| CyberPanel | OpenLiteSpeed | Not expected (no nginx) |
| Kinsta, WP Engine, Cloudways | Managed nginx | Ask: managed hosts usually patch for you, but confirm |
LiteSpeed and OpenLiteSpeed servers aren’t affected by the nginx bugs. The kernel SCTP flaw is still worth checking on those hosts, though nobody can reach it without a foothold first.
Questions to ask your provider:
- When will you ship nginx 1.31.9/1.30.7 (or a backport), and will nginx be restarted automatically?
- Is HTTP/2 or HTTP/3 enabled on my servers, and can I disable it in the meantime?
- Are you blocking or patching the kernel SCTP module on the host?
- For container platforms: do my containers share the host kernel, and when do images get rebuilt?
Provider responses:
- GridPane: No public statement yet.
- RunCloud: No public statement yet.
- Cloudflare: Cloudflare says its edge, a heavily modified nginx fork, was patched globally before disclosure. It also says origins reachable only through its proxy are protected while you update, because it terminates client HTTP/2 and HTTP/3 itself.
- F5: F5 says BIG-IP, BIG-IQ, F5OS and related products are not vulnerable.
Infrastructure Beyond WordPress
nginx is everywhere around a WordPress fleet, not just on the web servers. Check:
- Reverse proxies and load balancers (Nginx Proxy Manager, plain nginx in front of apps)
- Docker hosts using the
nginxornginx:alpineimages. The plainnginx:alpinetag still pointed at 1.31.8 on disclosure afternoon, so pinnginx:1.31.9-alpineor newer. - Kubernetes clusters with ingress-nginx (no patch coming)
- Monitoring, status pages and dashboards (Grafana, Uptime Kuma) fronted by nginx
- Git servers, CI and self-hosted tools with an nginx front end
- Appliances and NAS devices that ship nginx (check the vendor)
Not affected: Apache-only and LiteSpeed/OpenLiteSpeed servers, Caddy and Traefik (they don’t use nginx), and F5 BIG-IP.
The Linux Kernel SCTP Flaw
The sixth bug is what makes this “nginx2root” rather than “nginx2shell”. It is a use-after-free in the kernel’s SCTP code, present since Linux 4.15. As of disclosure it has no CVE and no kernel patch.
By itself it is a local privilege escalation: an attacker needs to be running code on the box first. Any of the five nginx bugs provides that, and so does a compromised WordPress plugin running as the PHP user. On a shared WordPress server, that makes this kernel bug worth handling on its own.
Hardly any WordPress host uses SCTP. Xint’s mitigation is to stop the module from loading by adding install sctp /bin/false to a file in /etc/modprobe.d/. This doesn’t unload a module that is already loaded and doesn’t help if SCTP is built into the kernel, so check both. On container platforms, containers share the host kernel, so this belongs to whoever runs the host.
Watch your distro’s kernel advisories for a CVE and patch, then reboot into the fixed kernel when it ships.
Installing the Fix
- GridPane / RunCloud: Wait for the vendor’s nginx update and watch their status pages and changelogs. Confirm nginx was restarted, not just reloaded.
- Debian / Ubuntu / RHEL: Update the nginx package once your distro publishes it, then
systemctl restart nginx. Check the full package version against USN, the Debian security tracker or RHSA, notnginx -v. If you use the nginx.org repository, 1.31.9/1.30.7 is available now. - Docker / Enhance / FlyWP: Pull the patched image (official
nginximages:latest/mainline→ 1.31.9,stable→ 1.30.7) and recreate the containers. For managed container platforms, the vendor has to rebuild.
Mitigations to Reduce Exposure
- Put the origin behind Cloudflare’s proxy and lock it down. Proxy the DNS records and restrict ports 80/443 to Cloudflare IPs so nobody can reach nginx’s HTTP/2 directly. Cloudflare says this protects you while you update. (Vendor claim.)
- Disable HTTP/2 if you can’t patch: set
http2 off;on nginx 1.25.1 and later, or removehttp2fromlistenon older versions. This blocks CVE-2026-123007 and CVE-2026-123633. On GridPane and RunCloud, ask the vendor first, because hand edits to panel-managed config may be overwritten. - Disable HTTP/3/QUIC if you enabled it.
- Block the SCTP kernel module (see above).
- Restart, don’t reload, after any change so old workers go away.
Xint’s write-up covers the less common configs (resolver/mirror, mail proxy) in detail.
Detecting Exploitation
Xint suggests watching for nginx worker crashes (signal 11 in error.log, coredumpctl), odd long-lived connections with high inbound and low outbound bytes, and, the clearest sign, a shell or other process spawned by an nginx worker. An auditd execve rule on the worker user records that from now on, but it can’t see anything that happened before you installed it.
For the full process of checking a server for compromise, see How to Check a Linux Server for Intrusion.
FAQ
Am I safe if my site is behind Cloudflare?
Mostly, if nginx is reachable only through Cloudflare’s proxy. Cloudflare says it terminates HTTP/2 and HTTP/3 at its edge. If your origin IP is reachable directly, you’re still exposed. Patch either way.
Does disabling HTTP/2 hurt WordPress performance?
Some, especially on asset-heavy pages, but it’s a temporary trade-off. Behind Cloudflare, visitors still get HTTP/2 or HTTP/3 to the edge.
I’m on OpenLiteSpeed. Do I need to do anything?
Not for the nginx bugs. Block the SCTP module anyway, since any code execution on the box (a bad plugin, for example) could chain into it.
Why does nginx -v still show an old version after updating?
Distros backport security fixes without bumping the upstream version. Check the package version against your distro’s advisory.
Updates
- November 18, 2026: Initial post.
Sources
- Xint — NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching
- Business Wire — PSA: Immediately Patch NGINX Web Servers
- Precursor Security — NGINX2Root live updates
- Aikido — nginx2root: Critical nginx RCE vulnerabilities and how to fix them
- CIRCL TR-105 — NGINX2ROOT
- nginx security advisories
- NVD: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425
