A decade-old NGINX HTTP/2 flaw, and what to do about it

Long-exposure light trails flowing in parallel lanes at night, one magenta trail breaking out of its lane Long-exposure light trails flowing in parallel lanes at night, one magenta trail breaking out of its lane Long-exposure light trails flowing in parallel lanes at night, one magenta trail breaking out of its lane
Photo of Oliver Pinson-Roxburgh

Oliver Pinson-Roxburgh

CEO and Co-Founder

19th Nov 2026

If your business runs NGINX with HTTP/2 enabled, upgrade to version 1.31.9 or 1.30.7 (or the fixed NGINX Plus builds) as soon as you reasonably can. On 18 November 2026, F5 released fixes for five serious NGINX vulnerabilities, each rated 9.2 out of 10 on CVSS 4.0. The most notable, CVE-2026-123007 (nicknamed "nginx2root"), has existed in the code since version 1.9.5 in September 2015.

What the flaw is

An attacker who can reach a server's HTTP/2 port can, under the right conditions, run their own code on that server without logging in. F5 says this is possible where ASLR (a memory-protection feature) is off or can be worked around. Independent security researchers have shown working code execution in their tests, including against servers on AWS, GCP and Azure.

Code that runs this way has the same rights as an NGINX worker process, not full control of the machine. To go further, an attacker needs a second weakness. One research team demonstrated that with a separate bug in the Linux kernel's SCTP code they could get root access, even from inside a Docker container.

How worried should you be?

There is no need to panic, but this is worth acting on promptly. As of 19 November, neither F5 nor CERT-EU had reported any real-world attacks, and the flaw was not on CISA's Known Exploited Vulnerabilities list. Some practical limits also apply. One published version of the attack needed roughly 128 GB of traffic and relied on specific CPU features; on connections slower than about 300 Mbit/s it would likely time out.

The counterweight is that public proof-of-concept code already exists, and attack techniques tend to improve once details are out. Waiting for the first reported attack before patching leaves very little room.

Who is affected

According to the nginx.org security advisories, every open-source NGINX release from 1.9.5 to 1.30.6, and from 1.31.0 to 1.31.8, is affected, including the October 2026 security releases. NGINX Plus is also affected. Some cloud and container images, and Linux distribution packages, may lag behind the upstream fix, so it is worth checking each source of NGINX you rely on.

Products built on NGINX are affected too. F5 has released fixes for NGINX Ingress Controller (5.8.0 and 2026-lts-r11), NGINX Gateway Fabric (2.9.0), NGINX Instance Manager (2.25.0), F5 WAF for NGINX (5.16.2 and 5.14.4) and F5 DoS for NGINX (4.13.0). NGINX App Protect WAF and DoS, and older Ingress Controller and Gateway Fabric branches, have no fix yet. If you run NGINX in Kubernetes, check F5's advisory for your Ingress Controller or Gateway Fabric version.

Four other flaws fixed

The same release fixes four further issues, each reachable only in a particular setup: HTTP/2 combined with proxying under heavy connection load, certain resolver and subrequest configurations, HTTP/3, and NGINX used as a mail proxy. Upgrading to 1.31.9 or 1.30.7 addresses all five, along with several lower-severity issues that the workarounds below do not cover.

What we suggest

The steps below walk through four stages: find out whether your servers are exposed, upgrade or apply a temporary workaround, confirm the fix has taken effect, and keep an eye out for warning signs. Most teams can complete the checks in under an hour. If you would like a second pair of eyes on any of it, get in touch with our team.

Step 1: Check whether you are exposed

You are exposed to the main flaw if a server runs an affected NGINX version and accepts HTTP/2. Work through these checks for every NGINX instance, including containers, load balancers and reverse proxies.

  1. Find your NGINX version. On each host, run nginx -v. Open-source versions 1.9.5 to 1.30.6 and 1.31.0 to 1.31.8 are affected. If NGINX came from your Linux distribution, also check the full package version (for example with dpkg -l nginx or rpm -q nginx), because distributions sometimes backport fixes without changing the number nginx -v shows.
  2. Check whether HTTP/2 is switched on in the config. Ask NGINX to print its full configuration, including any included files, and search it for http2:
    sudo nginx -T 2>&1 | grep -n "http2"
    HTTP/2 is on if a listen line contains http2 (for example listen 443 ssl http2;) or a server block contains http2 on;. This shows the configuration on disk, which may differ from what is running if NGINX has not been restarted since it last changed, so also do the outside check below.
  3. Confirm from the outside. Test whether the server actually offers HTTP/2:
    openssl s_client -connect your-server.example:443 -servername your-server.example -alpn h2 </dev/null 2>/dev/null | grep ALPN
    If the output shows ALPN protocol: h2, the server accepts HTTP/2. Run it once for each website hostname the server hosts, as HTTP/2 can be on for one site and off for another. If you connect by IP address, put the IP after -connect and the website hostname after -servername. This check only covers HTTPS. NGINX can also accept HTTP/2 without encryption (a listen line with http2 but no ssl), which is exposed too; curl --http2-prior-knowledge -sI http://your-server.example:8080/ returning HTTP/2 confirms it on that port.
  4. Test the origin, not just the CDN. If you sit behind a CDN or cloud load balancer, run the outside check above against the NGINX origin server directly. An origin that only speaks HTTP/1.1 cannot be reached through this HTTP/2 flaw, even if the CDN in front uses HTTP/2.
  5. Check for the other four flaws' setups. Note whether any server uses HTTP/3, acts as a mail proxy, or uses SSI or mirror subrequests with a proxied server name built from variables. These matter for the workarounds in step 2.

If you are a Defense.com customer, Vulnerability Scanning can help you find internet-facing NGINX servers you may have forgotten about, and Application Scanning checks the websites they serve. Treat scan results as a starting point and not a final answer. Many servers hide their NGINX version, and distribution packages are often patched without the version number changing, so confirm with the checks above.

The setup each of the five NGINX flaws needs before it can be reached
Flaw Only reachable when
CVE-2026-123007 (nginx2root)HTTP/2 is on
CVE-2026-123633HTTP/2 is on, requests are proxied to a backend, and the worker is close to its worker_connections limit
CVE-2026-123634A proxied server name is built from variables, together with an SSI or mirror subrequest that looks up that name
CVE-2026-121810HTTP/3 is on
CVE-2026-113425NGINX is used as a mail proxy

Step 2: Upgrade, or apply a temporary workaround

Upgrading is the real fix; the workarounds only buy time. Open-source 1.31.9 and 1.30.7 fix all five flaws.

The NGINX version to upgrade to, by the version you run now
You run Upgrade to
NGINX Open Source 1.31.0 to 1.31.8 (mainline)1.31.9
NGINX Open Source 1.9.5 to 1.30.6, including older branches such as 1.281.30.7
NGINX Plus 37.1.0 to 37.2.0.137.3.0.1
NGINX Plus 37.0.0 to 37.0.7.137.0.8.1
NGINX Plus R34 to R36No fix listed by F5 yet; apply the workarounds below and plan a move to a supported 37.x build
NGINX Plus R33 and earlierOut of support and not assessed by F5; upgrade to a supported 37.x build

Doing the upgrade

  1. Official Docker images: the 1.31.9 and 1.30.7 tags (including Alpine variants) were available on Docker Hub from 18 November. Update your image tag and redeploy.
  2. Linux distribution packages: as of 19 November, Ubuntu had shipped fixed packages for all supported releases, including 26.04 LTS, 24.04 LTS and 22.04 LTS (older LTS releases through Ubuntu Pro). Debian had fixed only its unstable branch; packages for Debian 12 (bookworm) and 13 (trixie) were still waiting. Check Ubuntu's CVE page or the Debian security tracker for the fixed package version for your release, and use the workarounds until a fix lands. Alternatively, switch to the official nginx.org packages.
  3. Restart properly. After upgrading, do a full restart (systemctl restart nginx) or NGINX's live binary upgrade. A plain reload keeps the old program running, and existing connections can stay on old worker processes.

Temporary workarounds if you cannot upgrade yet

F5 has not published an official mitigation. These are our suggestions for reducing exposure until you can upgrade.

  • Turn off HTTP/2. This takes the vulnerable code out of the path for CVE-2026-123007 and CVE-2026-123633, but not the other three. On NGINX 1.25.1 and later, set http2 off; in each affected server block and remove http2 from its listen lines. On 1.9.5 to 1.25.0, remove http2 from the listen line, so listen 443 ssl http2; becomes listen 443 ssl;. Review every server block that shares the same listener, including IPv6 ([::]) listen lines, and not just the one for your main site. Clients fall back to HTTP/1.1, so sites keep working, though some may load slightly slower.
  • Turn off HTTP/3 where you use it, to remove the setup CVE-2026-121810 needs.
  • Resolver flaw (CVE-2026-123634): avoid SSI and mirror directives, and don't build a proxied server name from variables.
  • Mail proxy flaw (CVE-2026-113425): restrict mail proxy listeners to trusted networks only.
  • Block the kernel SCTP module on hosts that don't use SCTP, to close off the privilege-escalation route researchers demonstrated. Add the line install sctp /bin/false to a .conf file in /etc/modprobe.d/. This stops the module loading in future but won't unload one already loaded or disable SCTP built into the kernel, so a reboot may be needed.

After any configuration change, run nginx -t to check the config, then restart NGINX.

Steps 3 and 4: Confirm the fix and watch for warning signs

Once you have upgraded or applied a workaround, confirm it actually took effect, then keep an eye out for signs of earlier tampering.

Step 3: Confirm the fix

  • Run nginx -v again and check it shows 1.31.9, 1.30.7 or a fixed NGINX Plus build (or, for distribution packages, the fixed package version from your distribution's advisory).
  • Check that no old worker processes are still running: ps -o pid,lstart,cmd -C nginx should show all processes started after your upgrade.
  • If you turned off HTTP/2, rerun the outside check from step 1 for each hostname:
    openssl s_client -connect your-server.example:443 -servername your-server.example -alpn h2 </dev/null 2>/dev/null | grep ALPN
    The output should no longer show ALPN protocol: h2.
  • Rebuild and redeploy any container images that bundle NGINX, and confirm running containers use the new tag.
  • Record which servers were checked and when, so nothing gets missed.

Step 4: Look for signs of attack

CIRCL, the Luxembourg computer incident response center, suggests looking for the following. None of them proves an attack on its own, but any of them is worth investigating.

  • NGINX worker processes starting programs they normally wouldn't (for example a shell).
  • Workers crashing, exiting unexpectedly or leaving core dumps. CERT-EU suggests searching the NGINX error log for worker process … exited on signal, which points to exploitation attempts though not to successful code execution.
  • Long-lived HTTP/2 connections with a lot of incoming data but very few logged requests.
  • Unusual outbound connections or DNS lookups from the web server.

A clean access log is not proof that nothing happened. HTTP/2 control traffic used in this attack normally doesn't appear in access logs as requests, so check process, network and system logs too. If you find anything suspicious, isolate the host and follow your incident response process.

Sources: F5 advisory K000163926, the nginx.org security advisories, CERT-EU Security Advisory 2026-022, CIRCL TR-105, and the Ubuntu and Debian security trackers.

NGINX HTTP/2 flaw FAQs

As of 19 November 2026, no attacks had been reported and the flaw was not on CISA's Known Exploited Vulnerabilities list. Public proof-of-concept code exists, so that could change.

Not necessarily. What matters is whether your NGINX origin accepts HTTP/2 from anyone who can reach it. Test the origin directly.

Browsers fall back to HTTP/1.1 automatically, so sites keep working. Performance may dip slightly on pages with many resources.

No. A reload leaves the old program in memory. Do a full restart or a live binary upgrade.

This advisory is NGINX-specific. Apache HTTP Server had its own, unrelated HTTP/2 flaw this month: CVE-2026-119618, rated critical by Apache, affects versions 2.4.55 to 2.4.70 when mod_http2 is loaded. It was fixed in 2.4.71 on 11 November, so upgrade if you run an affected version.

Find the NGINX servers you've forgotten about

Vulnerability Scanning maps your internet-facing servers and checks them for known weaknesses, so you know what needs patching first.