Insights

NGINX2Root (CVE-2026-123007): Critical nginx HTTP/2 Flaw, Update Your nginx Servers Now

NGINX2Root nginx HTTP/2 vulnerability CVE-2026-123007: update nginx now

On 18 November 2026 the nginx project released fixes for a group of memory-safety vulnerabilities that researchers have named NGINX2Root. The most serious, CVE-2026-123007, is a flaw in nginx's HTTP/2 flow control that has been present in every release since version 1.9.5, published in 2015. F5, the company behind nginx, rates it 9.2 (Critical) on CVSS v4.0 and 8.1 (High) on CVSS v3.1. An attacker needs no account and no interaction from anyone: a crafted HTTP/2 connection to a vulnerable server is enough.

If you run nginx on a server you manage, update it now. This article explains what the vulnerability is, which versions are fixed and what to do if a patched package is not yet available for your operating system. Customers on shared, WordPress and managed hosting do not need to do anything.

The short version

nginx 1.9.5 to 1.31.8 is vulnerable when HTTP/2 is enabled, which is the case on most modern HTTPS websites. The fix is nginx 1.31.9 (mainline) or 1.30.7 (stable), followed by a full restart of nginx. VPS, dedicated server and colocation customers who run nginx must update their own installations, and can switch off HTTP/2 as a stopgap until a patched package is available for their operating system. Shared, WordPress and managed hosting customers need to do nothing.

What is NGINX2Root?

NGINX2Root is the name the security firm Xint gave to five vulnerabilities it found in nginx, together with a separate bug in the Linux kernel. Each nginx flaw can let a remote attacker crash nginx worker processes and, in the right conditions, run their own commands with the privileges of the nginx worker. The kernel bug is what puts "root" in the name: once an attacker is running code as the web server, it can be used to take full control of the machine. In Xint's tests the chain also broke out of a Docker container running nginx.

The headline flaw, CVE-2026-123007, sits in the code that tracks HTTP/2 send windows, the mechanism a browser and server use to pace how much data flows on each stream. A miscalculation in that accounting lets a client push nginx into reading and writing memory outside the buffer it should be using. Rapid7 found the same bug independently, and researchers have demonstrated working exploits in the lab.

The five nginx vulnerabilities are:

CVEWhere it isExposed whenAffected versions
CVE-2026-123007HTTP/2 flow controlHTTP/2 is enabled1.9.5 to 1.31.8
CVE-2026-123633HTTP/2 connection handlingHTTP/2 is enabled and nginx proxies to an upstream1.19.7 to 1.31.8
CVE-2026-121810HTTP/3 (QUIC) streamsHTTP/3 is enabled and nginx proxies to an upstream1.25.0 to 1.31.8
CVE-2026-123634DNS resolverresolver is set, proxy_pass takes its target from the request, and mirror is in use0.6.18 to 1.31.8
CVE-2026-113425Mail proxyThe mail proxy runs with auth_http0.5.33 to 1.31.8

The same nginx releases fix several other, less severe issues, so updating is worthwhile even if none of the conditions above apply to you.

At the time of writing, 19 November 2026, there are no confirmed reports of these flaws being used in real attacks and none of them is in CISA's Known Exploited Vulnerabilities catalogue. With the details public and exploits already demonstrated, we do not expect that to last.

Which versions are fixed?

SoftwareStatus at the time of writing
nginx mainline (nginx.org)Fixed in 1.31.9
nginx stable (nginx.org)Fixed in 1.30.7
Official nginx Docker imagesFixed in the 1.31.9 and 1.30.7 tags. Pull the image again and recreate your containers.
Alpine Linux 3.24 and edgeFixed in 1.30.7-r0
Debian 12 and 13Listed as vulnerable, fixed packages pending
Ubuntu 16.04 to 26.10Listed as vulnerable, fixed packages pending
NGINX PlusSee F5 advisory K000163926 for the fixed release for your version
OpenResty and other nginx-based buildsCheck with the maintainer. A build is affected if the nginx version it bundles is.

Distributions usually backport security fixes without changing the version that nginx -v prints. Compare the full package version with your vendor's advisory instead of relying on the upstream numbers above.

What you need to do

Shared, WordPress and managed hosting customers

Nothing. The server software on these services is maintained by QUAPE, and there is no change to how your website or email works.

VPS, dedicated server and colocation customers

You manage the software on these services, so if nginx is installed, you need to update it yourself. Remember that nginx is often present without being installed by hand: many control panels, reverse proxies, load balancers, Kubernetes ingress controllers and container images include it.

  1. Find out whether you run nginx and which version: nginx -v on the server or inside the container.
  2. See which of the conditions apply to your configuration: nginx -T | grep -nE 'http2|http3|quic|resolver|mirror|auth_http'.
  3. Update to a fixed release. Use nginx 1.31.9 or 1.30.7 from nginx.org, or the patched package from your distribution once it is published (apt update && apt upgrade on Debian and Ubuntu, dnf upgrade on RHEL-family systems).
  4. Restart nginx, do not just reload it. A reload can leave old worker processes serving existing connections with the vulnerable code. Use systemctl restart nginx.
  5. Rebuild and redeploy any container image that bundles nginx.

If you would like QUAPE to update a server for you, open a support ticket from your account and our engineers will schedule it.

If you cannot patch yet

If your operating system has not published a fixed package, these steps reduce your exposure in the meantime. They are stopgaps, not fixes.

  • Switch off HTTP/2. This blocks CVE-2026-123007 and CVE-2026-123633. On nginx 1.25.1 and newer, set http2 off;. On older versions, remove http2 from your listen lines. Then restart nginx. Websites keep working over HTTP/1.1, but anything that depends on HTTP/2, such as native gRPC, will stop.
  • Switch off HTTP/3 if you use it and proxy to an upstream: remove the QUIC listeners, set http3 off; and remove the Alt-Svc header. This addresses CVE-2026-121810.
  • Use fixed upstreams. Point proxy_pass at a named upstream group instead of a hostname built from the request. This addresses CVE-2026-123634.
  • Keep the mail proxy private. Bind mail listeners to localhost or restrict them by firewall to trusted addresses. This addresses CVE-2026-113425.
  • Block the SCTP kernel module if you do not use it. The kernel bug in the chain is in SCTP, a protocol most web servers never need. Add install sctp /bin/false to a file in /etc/modprobe.d/. This does not unload a module that is already loaded and does not help where SCTP is built into the kernel. Watch for a kernel update from your distribution and apply it when it arrives.

Disabling HTTP/2 on its own is not the whole job. It leaves the other three nginx flaws open where their conditions apply.

Signs to watch for

If you notice nginx workers crashing or restarting without explanation, unfamiliar processes started by the web server user, or unexpected outbound connections on a server you manage, treat it as suspicious and contact support so we can investigate with you.

Timeline

  • 2015: the vulnerable HTTP/2 code ships in nginx 1.9.5.
  • 11 October 2026: Xint discovers the vulnerabilities.
  • 16 October 2026: Xint reports them to F5.
  • 10 November 2026: the fixes are validated.
  • 18 November 2026: nginx 1.31.9 and 1.30.7 are released and the advisories are published.

Questions

If you are unsure whether your server runs nginx or which version it has, open a support ticket from your account and we will check it with you. For anything else related to this advisory, reply to the notification email or contact our team.

References: nginx security advisories for CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425 (18 November 2026); F5 advisory K000163926; Xint, "NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching"; Ubuntu CVE tracker and Debian security tracker entries for CVE-2026-123007; CERT-EU security advisory 2026-022.