Security Digest · Nov 18, 2026 · Vulnerability · Other

nginx2root: Unauthenticated RCE in NGINX HTTP/2

Five NGINX worker RCE bugs, led by HTTP/2 flaw CVE-2026-123007 with a public PoC. Fixed in 1.30.7 and 1.31.9. Patch HTTP/2 servers this week.

Our verdict

Patch this week

A public exploit gets code execution in a lab and the last nginx bug like this was attacked within three days, but no attacks are reported yet and turning off HTTP/2 blocks the main bug, so patch internet-facing HTTP/2 servers in the next few days and use the workaround where no package exists.

Who must act: Anyone running NGINX Open Source 1.9.5 to 1.31.8 or NGINX Plus with HTTP/2 enabled on a reachable listener, especially internet-facing reverse proxies and container images built on older nginx bases.

Who can relax: Servers already running 1.30.7, 1.31.9 or a fixed distribution package after a full restart, and nginx instances that only speak HTTP/1.1 behind a CDN or load balancer that terminates HTTP/2.

Affected
NGINX Open Source 1.9.5 through 1.31.8 with HTTP/2 enabled (CVE-2026-123007)
NGINX Open Source 1.19.7 through 1.31.8 with HTTP/2 and proxying to an upstream (CVE-2026-123633)
NGINX Open Source with HTTP/3, request-time resolver plus mirror, or mail proxy auth_http configurations (CVE-2026-121810, CVE-2026-123634, CVE-2026-113425)
NGINX Plus 37.0.0 to 37.0.7.1 and 37.1.0 to 37.2.0.1; R33 through R36 listed as affected with no fix in those branches
Debian 12 and 13 nginx packages (no fix as of Nov 19, 2026)
Red Hat Enterprise Linux 8, 9 and 10 nginx packages (no errata as of Nov 19, 2026)
Fixed in
NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), released Nov 18, 2026
NGINX Plus 37.0.8.1 and 37.3.0.1
Ubuntu USN-9159-1, e.g. 24.04 nginx 1.24.0-2ubuntu7.20 and 22.04 nginx 1.18.0-6ubuntu14.23
Debian unstable nginx 1.30.6-4
Docker official images nginx:1.30.7 and nginx:1.31.9
CVSS
9.2 (v4.0, CNA)
EPSS
29.9% (percentile 98)
CISA KEV
Not listed
Exploitation
Public proof-of-concept
Severity
Critical

What to do

  1. Find every nginx that accepts HTTP/2: run nginx -v and nginx -T | grep -nE 'http2|http3|quic|resolver|mirror|auth_http' on each host and image.
  2. Upgrade to nginx 1.30.7 or 1.31.9, NGINX Plus 37.0.8.1 or 37.3.0.1, or your distribution's fixed package, then fully restart nginx; a reload does not replace the running binary.
  3. Rebuild container images from the refreshed nginx:1.30.7 or nginx:1.31.9 official images or a fixed distro base, and redeploy.
  4. Where no fixed package exists yet (Debian, RHEL, NGINX Plus R33 to R36), set http2 off; or remove http2 from listen directives on exposed servers, then confirm old workers exited.
  5. If you use HTTP/3, a request-time resolver with mirror, or the mail proxy, apply Xint's stopgaps: http3 off without an Alt-Svc header, fixed upstream groups, and mail listeners bound to loopback or firewalled.
  6. On hosts that do not use SCTP, add install sctp /bin/false under /etc/modprobe.d/ to cut the kernel root path Xint chained with these bugs.

How to check if you are affected or compromised

  • Search error logs for worker crashes: grep -E 'exited on signal (6|11)' /var/log/nginx/error.log*. CERT-EU treats these as possible exploitation attempts.
  • Look for shells, curl, wget or other child processes started by nginx worker processes in EDR, auditd or container runtime logs.
  • Confirm the patched binary is the one running: compare nginx -v and the package version with your vendor's fixed build, and check that worker start times (ps -o lstart= -C nginx) postdate the upgrade.
  • If a worker ran attacker commands, check the host for root-level changes too, since Xint chained the nginx bugs with a Linux SCTP flaw to reach root, including from a Docker container.

What happened#

On November 18, 2026, the nginx team released nginx 1.30.7 (stable) and 1.31.9 (mainline) with fixes for ten vulnerabilities. The same day, Xint published nginx2root, a write-up of five of them. Xint says each one alone gives an unauthenticated attacker code execution as the nginx worker in the right configuration.

The headline bug is CVE-2026-123007, memory corruption in HTTP/2 flow control that the nginx advisory list rates "major." Per Wiz, a connection's send window can be pushed past the HTTP/2 maximum, a bounds check then underflows, and the result is an out-of-bounds copy on the TLS send path. F5, the CVE numbering authority, scores it 8.1 (CVSS 3.1) and 9.2 (CVSS 4.0), and says code execution needs ASLR to be disabled or bypassed. It dates to 2015.

The other four are use-after-frees: CVE-2026-123633 in HTTP/2 proxying when a worker runs low on worker_connections, CVE-2026-121810 in HTTP/3, CVE-2026-123634 in the DNS resolver and CVE-2026-113425 in the mail proxy. The changelog lists five lesser fixes too.

Exploit code is public. Rapid7's Stephen Fewer released a proof of concept that gets unauthenticated RCE against nginx 1.31.8 in a Docker container. Wiz confirmed RCE with an ASLR bypass on official builds, and Xint says its exploit worked on AWS, GCP and Azure. Xint also chained an unpatched Linux kernel SCTP flaw to get root, including from inside a Docker container.

Who is affected#

CVE-2026-123007 affects NGINX Open Source 1.9.5 through 1.31.8 with HTTP/2 enabled, meaning a listen ... http2 or http2 on; line. Tenable says it needs HTTP/2 over TLS. CVE-2026-123633 affects 1.19.7 and later when HTTP/2 traffic is proxied to a backend, the standard reverse-proxy setup. The other three need HTTP/3, a resolver with request-built proxy_pass and mirror, or the mail proxy. NGINX Plus 37.x before 37.0.8.1 and 37.3.0.1 is affected, and the CVE record lists R33 through R36 as affected with no fix in those branches. Xint found 98.9% of nginx hosts with a visible version on Shodan in range, though backports and disabled HTTP/2 make version strings an imperfect guide.

As of November 19, Ubuntu has shipped USN-9159-1 for 16.04 through 26.10, with 20.04 and older through Ubuntu Pro. The Debian tracker shows only unstable fixed, and bookworm and trixie are still vulnerable. Red Hat rates the bug Critical and lists nginx in RHEL 8, 9 and 10, the 3scale APIcast gateway and Red Hat Hardened Images as affected, with no errata yet. The official Docker images for 1.30.7 and 1.31.9 were pushed on November 18 and 19.

Do you really need to act?#

Yes, if you serve HTTP/2 from nginx, but this is a fast patch, not an all-nighter. nginx is everywhere, no login is needed, and a working exploit is public.

Several things keep this short of an emergency. CERT-EU and Tenable report no exploitation in the wild, and CISA's assessment in the CVE record says "Exploitation: none" and "Automatable: no." F5 rates attack complexity High. The public exploit's README says it will likely fail against a server with concurrent clients or a long-running worker. Wiz calls both HTTP/2 bugs difficult to exploit remotely and says a CDN or WAF that terminates HTTP/2 may partly mitigate them.

The reasons not to wait are concrete too. In May, NGINX Rift (CVE-2026-42945), the previous nginx memory-corruption bug with a public proof of concept, was exploited three days after disclosure. Failed attempts still crash workers. And the workaround is cheap: turning off HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633.

What to do now#

  1. Inventory: run nginx -v and nginx -T | grep -nE 'http2|http3|quic|resolver|mirror|auth_http' on every host and in every image that ships nginx.
  2. Upgrade to 1.30.7 or 1.31.9, NGINX Plus 37.0.8.1 or 37.3.0.1, or your distribution's fixed package (on Ubuntu, apt update && apt upgrade). Then run systemctl restart nginx, because a reload keeps the old binary running.
  3. Rebuild container images from nginx:1.30.7, nginx:1.31.9 or a fixed distro base and redeploy.
  4. Where no fix exists yet (Debian stable, RHEL, NGINX Plus R33 to R36), disable HTTP/2 on exposed listeners: http2 off; on 1.25.1 and later, or remove http2 from listen lines. Run nginx -t && systemctl reload nginx and confirm old workers have exited.
  5. For the other three bugs, Xint recommends http3 off with no Alt-Svc header, fixed upstream groups instead of request-time DNS, and mail listeners bound to loopback. If you do not use SCTP, add install sctp /bin/false to a file in /etc/modprobe.d/.

How to tell if you were hit#

Attempts crash workers, so start with grep -E 'exited on signal (6|11)' /var/log/nginx/error.log*. CERT-EU treats these lines as possible attempts, not proof of compromise. Then look in EDR, auditd or container logs for shells, curl or wget started by nginx workers (www-data or nginx). If you find code execution, check for root-level changes too and rotate TLS keys and upstream credentials. After patching, confirm worker start times (ps -o lstart= -C nginx) are later than the upgrade.

Timeline#

  • — Xint discovers the vulnerabilities.
  • — Xint reports them to F5 through HackerOne.
  • — nginx 1.30.7 and 1.31.9 released. Xint, Wiz and CERT-EU publish; Rapid7's proof of concept is public.
  • — Ubuntu ships USN-9159-1 and the official Docker images are rebuilt. Debian stable and RHEL fixes are not yet available.

Vulnerability records

  • CVE-2026-123007 · This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2.
  • CVE-2026-123633 · When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request…
  • CVE-2026-121810 · Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3.
  • CVE-2026-123634 · This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI)…
  • CVE-2026-113425 · When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process.

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. nginx.org — nginx 1.30.7 stable and 1.31.9 mainline released with vulnerability fixes nginx.org
  2. nginx.org — nginx security advisories nginx.org
  3. nginx.org — Changes with nginx 1.31.9 nginx.org
  4. CVE record — CVE-2026-123007 (F5) cve.org
  5. CVE record — CVE-2026-123633 (F5) cve.org
  6. F5 — K000163926: NGINX ngx_http_v2_module vulnerability CVE-2026-123007 my.f5.com
  7. Xint — nginx2root: remote code execution in nginx xint.io
  8. Wiz Research — NGINX HTTP/2 RCE vulnerabilities wiz.io
  9. Stephen Fewer (Rapid7) — CVE-2026-123007 proof of concept github.com
  10. Ubuntu — CVE-2026-123007 ubuntu.com
  11. Debian security tracker — CVE-2026-123007 security-tracker.debian.org
  12. Red Hat — CVE-2026-123007 access.redhat.com
  13. Docker Hub — nginx official image hub.docker.com
  14. CERT-EU — Security Advisory 2026-022: Critical vulnerabilities in Nginx cert.europa.eu
  15. Tenable — NGINX2Root FAQ: five vulnerabilities in NGINX tenable.com

Coverage and analysis

  1. Help Net Security — Attackers are exploiting critical NGINX vulnerability (CVE-2026-42945) helpnetsecurity.com