Security

Nginx Vulnerability CVE-2026-123007: Update to 1.30.7 or 1.31.9, or Turn Off HTTP/2

An aerial drone photograph at golden hour of a wide river delta splitting into many shining channels across green and sandy land, the main river flowing in from the top and fanning out evenly, a visual for the nginx vulnerability in the reverse proxy that sits in front of many websites and splits traffic to them

A critical nginx vulnerability, CVE-2026-123007, can let an attacker corrupt memory and possibly run code over HTTP/2 without logging in. Nginx fixed it on November 18, 2026 in 1.30.7 (stable) and 1.31.9 (mainline), along with nine other flaws. Every open source release from 1.9.5 through 1.31.8 with HTTP/2 turned on is affected.

Nginx sits in front of a large share of managed WordPress and Drupal hosting, often as a reverse proxy or load balancer. It also runs inside control panels like Plesk and cPanel. This post covers what the flaws are, who is exposed, which packages fix them, NGINX Plus status, and the HTTP/2 stopgap. Facts are as of November 20, 2026.

The short version: update nginx to 1.30.7 or 1.31.9, or to your distribution’s fixed package, then reload it. Debian and Ubuntu ship fixes now. Red Hat had no fixed packages yet in its November 19 bulletin. If you cannot update, turn HTTP/2 off. If a host runs your server, ask them in writing whether it is patched.

What the nginx vulnerability is

The nginx security advisories page lists CVE-2026-123007 as "Memory corruption in HTTP/2 flow control," with major severity. The 1.31.9 change log says the overflow can crash a worker process "or might have potential other impact."

F5, which owns nginx, gives more detail in advisory K000163926. Under certain traffic, the HTTP/2 flow control window can pass its allowed limit. That can cause a heap buffer overflow, usually followed by a worker crash. F5 adds that attackers "can execute code" when ASLR is off or can be bypassed. ASLR is the memory layout shuffling that makes such attacks harder.

F5 scores it 8.1 (High) on CVSS 3.1 and 9.2 (Critical) on CVSS 4.0. Our guide to reading a CVSS score explains why the two numbers differ. F5 says it is a data plane issue only, with no control plane exposure. F5 lists the mitigation as "None." Red Hat and Wiz describe turning off HTTP/2 as a stopgap, covered below.

Red Hat’s security bulletin RHSB-2026-019 rates it Critical and calls the set "NGINX2Root." It says "A proof of concept is publicly available."

How hard is the nginx vulnerability to exploit?

The researchers who found it say real attacks face limits. Rapid7’s write-up describes its public exploit. Rapid7 reports these conditions:

  • A lot of traffic. About 128 GB of HTTP/2 data per attempt. That takes about two minutes at 10 Gbit/s and about seventeen minutes at 1 Gbit/s.

  • A time limit. Rapid7 points to nginx’s default one-hour connection lifetime. It says links slower than about 300 Mbit/s would likely run out of time.

  • Specific CPUs. The known exploit relies on a glibc memory copy routine chosen on x86-64 CPUs with certain AVX-512 features. Rapid7 says other methods may exist but none are known.

  • Worker rights only. Code runs as the nginx worker, not root, as far as Rapid7 has shown.

Rapid7 also says proxied HTTP/2 connections will likely not pass the attacker’s frames through in a usable way. Wiz Research, another finder, says it "will not be releasing these exploits at this time."

As of November 20, F5, Red Hat, Rapid7 and Wiz do not report attacks in the wild. A public exploit lowers the bar, so treat this nginx vulnerability as urgent.

The other nine fixes

The November 18 release fixes ten CVEs in all. Red Hat also rates three others Critical on its systems: the HTTP/2 and HTTP/3 use-after-free bugs and the mail proxy bug. Here is the full list from nginx.org.

CVE What it is Nginx severity
CVE-2026-123007 HTTP/2 flow control memory corruption Major
CVE-2026-118899 Endless loop reading request body over TLS 1.3 Major
CVE-2026-113425 Use-after-free in the mail proxy Major
CVE-2026-123633 HTTP/2 use-after-free Medium
CVE-2026-121810 HTTP/3 use-after-free Medium
CVE-2026-123634 Resolver use-after-free Medium
CVE-2026-120967 Stream module client certificate SNI bypass Medium
CVE-2026-125283 Buffer overflow with alias and try_files Minor
CVE-2026-123640 Stream ssl_preread validation Minor
CVE-2026-120993 PROXY protocol v2 crash, 1.31.x only Minor

The stable 1.30.7 release fixes nine of them. The PROXY protocol bug only affects 1.31.4 through 1.31.8, so 1.30.x never had it. If CVE numbers are new to you, start with what a CVE is.

The 1.31.9 change log also lists two behavior changes. Header lines without a colon are now rejected. Requests are rejected if a chunked body has "too much framing overhead." Test odd clients and API callers after you update.

Who is exposed to the nginx vulnerability

For CVE-2026-123007, two things must be true:

  • The version is in range. Nginx lists 1.9.5 through 1.31.8 as vulnerable.

  • HTTP/2 is on. F5 says the issue affects configurations that use HTTP/2. Red Hat says exploitation requires a server that accepts HTTP/2.

Many hosts turn HTTP/2 on for HTTPS sites because it speeds up page loads. Check yours rather than assume.

NGINX Plus is affected too. F5 lists Plus 37.1.0 through 37.2.0.1 (fixed in 37.3.0.1) and 37.0.0 through 37.0.7.1 (fixed in 37.0.8.1). F5 lists Plus R34 through R36 as affected with no fix. F5 also lists fixes for NGINX Ingress Controller (5.8.0 and 2026-lts-r11), NGINX Gateway Fabric (2.9.0) and NGINX Instance Manager (2.25.0). BIG-IP is not affected, per F5.

Fixed packages by distribution and panel

Most servers get nginx from the operating system or a control panel. Here is what each showed as of November 20.

Source Fixed package Notice
nginx.org source 1.30.7 stable, 1.31.9 mainline November 18
Debian 13 (trixie) 1.26.3-3+deb13u11 DSA-6642-1
Debian 12 (bookworm) 1.22.1-9+deb12u11 DLA-4918-1
Ubuntu 26.04 LTS 1.28.3-2ubuntu1.13 USN-9159-1, November 19
Ubuntu 24.04 LTS 1.24.0-2ubuntu7.20 USN-9159-1
Ubuntu 22.04 LTS 1.18.0-6ubuntu14.23 USN-9159-1
RHEL 8, 9, 10 No errata yet RHSB-2026-019, November 19
cPanel EasyApache 4 ea-nginx 1.31.9 EA4 25.98, November 19
Plesk Obsidian nginx 1.30.7 18.0.82 Update 4 and 18.0.81 Update 9

The Debian versions come from Debian’s security tracker, which still lists testing (forky) as vulnerable. The Ubuntu versions come from Ubuntu’s CVE page, which rates the nginx vulnerability High priority "because this is an RCE." Ubuntu 20.04, 18.04 and 16.04 get fixes only through Ubuntu Pro.

Red Hat’s bulletin lists RHEL 10, RHEL 9 and the RHEL 8 nginx 1.24 stream as affected, and says fixes are being expedited. The cPanel update is in the EasyApache 4 change log, and the Plesk updates are in the Plesk Obsidian change log.

Look at the Ubuntu and Debian rows. They fix the flaw in packages built on nginx 1.18, 1.22, 1.24 and 1.26. So nginx -v shows the base version, not whether the fix is in. Check the full package version with dpkg -l nginx or rpm -q nginx, as we explained for the Apache HTTP/2 vulnerability.

How to check for HTTP/2 and turn it off

These checks are standard nginx administration unless noted.

  1. Find HTTP/2 in the config. Run grep -rn http2 /etc/nginx/. Look for http2 on a listen line, or an http2 on; directive.

  2. Test from outside. Run curl -sI --http2 https://example.org against your site. A first line of HTTP/2 200 means HTTP/2 is on.

  3. Turn it off if you cannot patch. Red Hat and Wiz give the same steps. Remove the http2 parameter from listen lines. On nginx 1.25.1 and later, also set http2 off; in each affected server block.

  4. Reload and confirm. Run nginx -t, then reload nginx. Wiz says to confirm old worker processes have exited.

Red Hat also lists stopgaps for the other flaws. Remove the quic parameter and set http3 off; for the HTTP/3 bug. Remove mail blocks if you do not use the mail proxy. Turn HTTP/2 back on after you update.

Turning off HTTP/2 is a stopgap. Install the fixed build, confirm nginx reloaded, then turn HTTP/2 back on.

Reverse proxies in front of WordPress and Drupal

The nginx vulnerability sits in the web server, before PHP or your CMS sees the request. WordPress, Drupal, plugin and module updates do not cover it.

Many setups put nginx in front of Apache or PHP-FPM as a reverse proxy. The nginx at the edge is usually the one that speaks HTTP/2 to the internet, so patch that layer first. If that nginx is managed by a host, ask them three things in writing. Which nginx build is running? Is HTTP/2 on? When did nginx reload on the fixed build?

A CDN in front of nginx may help, based on Rapid7’s note about proxied connections. It helps only if your origin refuses direct connections. If attackers can find the origin IP address, they can skip the CDN.

Check one more setting while you are in the config. This week’s PHP security release fixed a PHP-FPM request smuggling flaw. It needs nginx with fastcgi_keep_conn on. Leave that setting off until PHP is updated too.

Managed platforms often run their own web stack and patch it for you. Our guide to choosing a managed WordPress host covers what those plans include. Even so, ask.

Frequently Asked Questions

What is the nginx vulnerability CVE-2026-123007?

A memory corruption bug in nginx’s HTTP/2 flow control. F5 says it can crash a worker and, if ASLR is off or bypassed, let an attacker run code.

Which nginx versions are affected?

Open source 1.9.5 through 1.31.8 with HTTP/2 on. Nginx 1.30.7 and 1.31.9 fix it. Distribution packages backport the fix to older base versions.

Is the nginx vulnerability being exploited?

F5, Red Hat, Rapid7 and Wiz do not report attacks in the wild as of November 20, 2026. A public proof of concept exists, so patch now.

Is NGINX Plus affected?

Yes. F5 lists fixes in Plus 37.3.0.1 and 37.0.8.1. Plus R34 through R36 are affected with no fix listed.

How do I know if HTTP/2 is on?

Search the nginx config for http2 on listen lines or an http2 on directive. You can also run curl with –http2 against the site and look for HTTP/2 in the reply.

What is the workaround if I cannot update?

Remove http2 from listen lines and set http2 off on nginx 1.25.1 and later. Then reload nginx. F5 itself lists no mitigation beyond updating.

My server shows nginx 1.24.0. Is it vulnerable?

It depends on the package. Ubuntu 24.04 ships the fix in 1.24.0-2ubuntu7.20. Check the full package version, not only the nginx number.

Does a CDN protect my site from the nginx vulnerability?

It may help, since Rapid7 says proxied HTTP/2 connections likely do not carry the attack. It does not help if attackers can reach your origin server directly.

Does the stable 1.30.7 release fix everything?

It fixes nine of the ten CVEs. The tenth, a PROXY protocol v2 bug, only affects mainline 1.31.4 through 1.31.8.

Digital Matters

Security Desk