DEV Community

Cover image for NGINX2Root: Check HTTP/2 Before You Panic
jamilxt
jamilxt

Posted on Edited on Originally published at jamilxt.com

NGINX2Root: Check HTTP/2 Before You Panic

Five nginx flaws were disclosed on November 18. The package version matters, but so does the configuration.

A server can run a vulnerable nginx build without exposing every attack path. That distinction matters after NGINX2Root, a group of five nginx vulnerabilities disclosed on November 18, 2026. One flaw affects HTTP/2 broadly. The other four need specific features or configurations.

The practical response is not to guess from nginx -v. Check the package, the active configuration, and whether the affected protocol is reachable. Then patch with the right package for your operating system.

What NGINX2Root means

The name comes from security researchers at Xint, who reported five nginx vulnerabilities and a separate Linux kernel flaw. The nginx issues can let an unauthenticated attacker corrupt memory in a worker process. Depending on the flaw and conditions, that can cause a crash or allow code execution as the nginx worker.

The word "root" needs care. The nginx vulnerabilities do not automatically grant root access. Xint says its researchers chained an nginx exploit with a separate Linux kernel SCTP flaw to reach root on the host. That is a second step, not the direct result of every nginx bug.

The most broadly relevant issue is CVE-2026-123007, a memory corruption flaw in HTTP/2 flow control. The nginx advisory lists affected official releases from 1.9.5 through 1.31.8. Fixed upstream releases are 1.30.7 and 1.31.9. nginx.org calls this flaw "major"; Ubuntu assigns it a High priority and records a CVSS 4.0 score of 9.2.

Five bugs, different doors

The five nginx issues do not all have the same trigger:

  • CVE-2026-123007: HTTP/2 enabled. This is the broadest configuration risk.
  • CVE-2026-123633: HTTP/2 connections are proxied to a backend, with a worker running low on available connections.
  • CVE-2026-123634: a proxy uses a variable server name together with a matching SSI or mirror subrequest.
  • CVE-2026-121810: HTTP/3 is enabled and requests are proxied to a backend, with additional worker-connection conditions.
  • CVE-2026-113425: nginx is configured as a mail proxy.

These conditions come from the nginx advisories and Xint's technical report. A reverse proxy with HTTP/2 deserves attention first, but disabling HTTP/2 only closes the two HTTP/2 paths. It is not a complete fix for every issue in the group.

Why the version string can mislead

Many Linux distributions backport security patches. They may keep an older upstream version number while adding a fix to the distribution package. So nginx -v alone cannot tell you whether a package is patched.

Check the full package version and the distribution's security tracker. On Ubuntu, for example:

nginx -v 2>&1
dpkg-query -W -f='${Package} ${Version}\n' 'nginx*'
apt-cache policy nginx
apt list --upgradable 2>/dev/null | grep -i nginx
Enter fullscreen mode Exit fullscreen mode

As of November 19, Ubuntu's tracker marked its nginx package for Ubuntu 24.04 as vulnerable to CVE-2026-123007. That is a dated status, not a permanent statement about Ubuntu's repositories. Check the tracker and package candidate again when acting.

Check whether HTTP/2 is actually enabled

Inspect nginx's effective configuration across included files. Any included file can define another listener:

sudo nginx -T 2>&1 \
  | sed 's/#.*//' \
  | grep -nE 'listen[[:space:]].*http2|^[[:space:]]*http2[[:space:]]+on[[:space:]]*;'
Enter fullscreen mode Exit fullscreen mode

A matching listen ... http2 or http2 on; line means the configuration enables HTTP/2. No output means it is not enabled in the configuration nginx reads from disk. If the configuration changed without a reload, the running workers may still have the previous settings.

For an internet-facing TLS endpoint, verify the negotiated protocol from outside the server:

openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>&1 \
  | grep -E 'ALPN protocol:|No ALPN negotiated'
Enter fullscreen mode Exit fullscreen mode

ALPN protocol: h2 means that endpoint accepted HTTP/2. If a CDN or load balancer sits in front, this test checks that front end, not necessarily nginx at the origin. Test the origin separately through an approved route.

What to do while waiting for a distribution patch

If HTTP/2 is enabled on an affected, unpatched nginx server, disable it temporarily on the affected listener and test the configuration before reloading. Clients can usually fall back to HTTP/1.1, but applications that depend on HTTP/2, such as native gRPC, may stop working.

Then check for the other feature-specific paths in the effective configuration. Do not remove proxy features blindly. Confirm whether they are in use, apply the matching vendor mitigation, and test affected routes.

When the operating system publishes a fixed package, install that package through its supported update channel. Do not assume that installing an upstream tarball over a distribution package is safer. After updating, restart nginx or use a supported live binary upgrade. A configuration reload alone does not replace an already-running nginx executable. Verify the new package version, service health, listener, and application routes afterward.

A practical decision rule

Treat these as separate questions:

  1. Does the installed build include a fix? Check the full package revision against the operating system's security advisory.
  2. Is an affected feature enabled? Inspect the effective nginx configuration for HTTP/2, HTTP/3, resolver and mirror patterns, and mail proxy settings.
  3. Can an external client reach that feature? Test the actual endpoint, accounting for any CDN or proxy in front.

If the build is unpatched but HTTP/2 is disabled, the main HTTP/2 attack path is currently disabled. That does not prove the server is patched, nor does it clear the other four vulnerabilities. Keep the temporary mitigation in place until the vendor package fixes the relevant code.

NGINX2Root is serious, but the useful response is specific: confirm package status, match configuration to each bug, reduce exposure where needed, then install and verify the vendor fix. A version string or a scary nickname is not a substitute for that check.

Sources

Top comments (0)