Two nginx flaws let outsiders run code on web servers

nginx HTTP/2 flaws let outsiders run code on web servers; fixed in 1.31.9 and 1.30.7

From the HARD Situation Room · First reported
rapid7.com: Rapid7
Screenshot: rapid7.com

Two flaws in nginx, the web server software behind many websites, let an attacker run code on a server without logging in. They affect nginx with HTTP/2 switched on, and researchers rate the first one critical. F5 says it has found no evidence of active exploitation so far, but Rapid7 has published proof-of-concept code for that flaw.

Current event. First reported . Details may change as more becomes known; updates will be added to the timeline.

What to do this week

  1. Find out whether you run nginx.Ask whoever looks after your website or server. If a host runs it for you, ask in writing: do you use nginx, which version is it on, and have you installed 1.31.9 or 1.30.7?
  2. Make sure it is on a fixed version.Use 1.31.9 (the newest release) or 1.30.7 (the stable release). NGINX Plus customers need 37.3.0.1 or 37.0.8.1. Restart nginx after updating. A Linux vendor that has patched an older version may keep the old number, so ask for its security notice.
  3. If you cannot update this week, switch HTTP/2 off.On nginx 1.25.1 and later, add http2 off; to each affected server block, then reload nginx. On older versions, remove http2 from the listen line. Test your sites afterwards, and switch HTTP/2 back on once you have updated.
  4. Replace ingress-nginx if you use it.Aikido recommends a maintained ingress controller, because no upstream fix is planned.
  5. Look for signs of trouble.Check nginx logs for worker processes that crash and restart, and for commands on the server that nobody started. Wiz calls these general warning signs, not proof that these flaws were used.

What happened

Two serious flaws in nginx let an attacker run their own code on a server without logging in. nginx is open source web server software that delivers pages to browsers for a very large share of websites. F5, the company that owns it, released fixed versions on 18 November 2026. Both flaws sit in the part of nginx that handles HTTP/2, a newer way for browsers and servers to exchange data.

nginx HTTP/2 flawsCVE-2026-123007 and CVE-2026-123633
Severity
Critical CVSS 9.2 for CVE-2026-123007, per Rapid7 and Wiz. nginx.org rates the second flaw medium.
Fixed in
nginx 1.31.9 (newest release) and 1.30.7 (stable release), both released 18 Nov 2026
Affected
nginx 1.9.5 to 1.31.8 for the first flaw; 1.19.7 to 1.31.8 for the second
Needs
HTTP/2 switched on. No login needed.
Attacks so far
F5 has found no evidence of active exploitation. Proof-of-concept code is public.
NGINX Plus
Fixed in 37.3.0.1 and 37.0.8.1. Releases R34 to R36 have no fix listed.
Timeline
22 Sep 2015: nginx 1.9.5 released, with the first flaw already in its code. 18 Nov 2026: flaws disclosed and fixed releases published.
What's known.Versions from Rapid7, Wiz and nginx.org. The exploitation status is F5's statement to The Register.

Wiz published research on both flaws, and Rapid7 published on the first. The Register reports that AI tools played a central role in finding the bugs. The first flaw, CVE-2026-123007, has been in nginx since version 1.9.5, released in September 2015, which makes it a decade old.

The full story2 more sections

How serious it is

Wiz says the first flaw can be triggered in default setups that have HTTP/2 switched on. Rapid7 says an attack needs a large volume of HTTP/2 traffic and is limited by bandwidth. Rapid7 has only shown code running with the permissions of nginx's worker process, the part that serves visitors. It has not shown an attacker reaching the server's administrator account.

The risk grows with a second step. Aikido describes a chain in which a separate flaw in Linux, the core of the operating system, takes that foothold up to root, the administrator account. Aikido says this works from inside a container too. The Register describes the same chain, moving from the nginx worker to root on the host.

Three more flaws, in nginx's DNS lookup code, its HTTP/3 code and its mail proxy, were fixed in the same releases. None of them needs HTTP/2, so switching HTTP/2 off does not close them.

F5 told The Register it has found no evidence of active exploitation of any of these flaws. Rapid7 has published proof-of-concept code for the first flaw, a working test that shows the flaw can be reproduced. Public code lowers the bar for attackers, so the update should not wait for routine maintenance.

Who is affected

If you run nginx yourself

You are in scope if you run nginx on your own server or virtual server and HTTP/2 is switched on. Whoever set it up can check the version by running nginx -v on the server. NGINX Plus customers have fixes in 37.3.0.1 and 37.0.8.1. Rapid7 lists no fix for Plus releases R34 to R36, so those users need to plan a move to a supported release.

If your website is hosted for you

Most people do not run nginx themselves. Their web host, or the company that builds and manages the site, does. The flaws are in nginx itself. A WordPress site is at risk only when nginx is the server behind it.

Some Linux systems ship their own nginx packages in the affected range. Aikido says Ubuntu 22.04 and 24.04, and Debian 12 and 13, do. Some vendors fix a flaw without changing the version number, so ask for their security notice rather than relying on the number alone.

If you use Kubernetes

ingress-nginx, a Kubernetes component that bundles an older nginx, was archived in March 2026. Aikido says no upstream fix is planned and recommends a maintained replacement.

Timeline
  1. HARD publishes its article, at High.

References8
  1. Rapid7 (). “CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)”. CVSS 9.2 and conditions for the first flaw, affected and fixed ranges for open source and NGINX Plus, and the lack of a Plus fix for R34 to R36.
  2. Wiz (). “Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007”. Both flaws are HTTP/2 issues rated critical at CVSS 9.2, the default-configuration point, affected and fixed versions, and the http2 off mitigation.
  3. nginx.org. “nginx security advisories”. Vendor's own list: affected ranges and the 'Not vulnerable: 1.31.9+, 1.30.7+' wording for all five CVEs, and the major and medium ratings.
  4. nginx.org (). “nginx changes log”. Mainline 1.31.9 dated 18 Nov 2026, with the HTTP/2 fixes listed in that entry.
  5. Aikido (). “nginx2root: Critical nginx vulnerabilities, including one RCE”. The five CVEs, the kernel chain to root, distribution versions in range, the ingress-nginx archive and no-fix status.
  6. The Register (). “AI found more critical bugs in another widely used technology running 225M websites”. F5's statement of no evidence of active exploitation, the finders, AI's role, the public proof-of-concept from Rapid7, and about 225 million websites.
  7. The Hacker News (). “10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers”. Feed summary only: the flaw dates to version 1.9.5, released 22 September 2015. The article itself returned a 403 when opened.
  8. Wordfence (). “PSA: Critical NGINX HTTP/2 Vulnerabilities: What WordPress Site Owners Should Know”. Feed summary only: WordPress site owners should watch for hosting provider guidance. The article itself did not load.

Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.