Two NGINX bugs let a stranger take over your web server. Update to 1.30.7 or 1.31.9 (CVE-2026-123007, CVE-2026-123633)

6 min read

How to fix CVE-2026-123007: upgrade NGINX to 1.30.7 or 1.31.9 (NGINX Plus 37.0.8.1 or 37.3.0.1), or turn HTTP/2 off until you can. Two HTTP/2 bugs disclosed Nov 18 let an attacker with no password run code on the server. One dates back to 2015.

BREAKING: Two NGINX bugs let a stranger take over your web server. Update to 1.30.7 or 1.31.9 (CVE-2026-123007, CVE-2026-123633)
On this page

Two newly disclosed bugs in NGINX, the web server in front of a large share of the world's websites and APIs, can let a stranger on the internet take over the server. They need no password and no help from anyone on your side. Both live in NGINX's HTTP/2 support, which most HTTPS sites turn on. F5, which maintains NGINX, published fixes on November 18, 2026. One of the two bugs, CVE-2026-123007, has been in the code since NGINX 1.9.5, released in 2015.

The fix is one upgrade: NGINX Open Source 1.30.7 (stable) or 1.31.9 (mainline), or NGINX Plus 37.0.8.1 or 37.3.0.1. If you can't upgrade today, turn HTTP/2 off until you can. This post is our operator read of F5's November security release. The HOL Guard evidence pack for CVE-2026-123007 is the source record.

How to fix

Upgrade NGINX to a release that fixes both HTTP/2 bugs:

  • NGINX Open Source stable: 1.30.7 or later.
  • NGINX Open Source mainline: 1.31.9 or later.
  • NGINX Plus: 37.0.8.1 (LTS) or 37.3.0.1. F5 lists 37.0.7.1 and 37.2.0.1 as the first builds fixed for CVE-2026-123633, but only 37.0.8.1 and 37.3.0.1 also fix CVE-2026-123007 and the rest of this release, so go straight to those.

Check what you run, and whether HTTP/2 is on:

nginx -v
nginx -T 2>/dev/null | grep -nE 'http2|listen .*443'

If nginx -v prints anything below 1.30.7 on the 1.30 line or below 1.31.9 on the 1.31 line, and the second command shows http2 on; or a listen ... http2 line, that server is exposed. Older branches such as 1.28 or 1.26 get no fix. Move them to 1.30.7.

The source tarballs are on nginx.org. When we checked on the morning of November 18, the official nginx Docker image had no 1.30.7 or 1.31.9 tag yet, and Linux distribution packages usually follow a few days behind. If you use either, watch for the rebuilt image or your distribution's security update, and use the workaround below in the meantime.

If you can't upgrade today

Both bugs need HTTP/2, so turning it off removes the attack path. This is the workaround F5 and the researchers recommend:

# NGINX 1.25.1 and later, in each affected server block
http2 off;

# older configs: remove "http2" from the listen line
listen 443 ssl;          # was: listen 443 ssl http2;

Then run nginx -t, reload, and confirm the old worker processes have exited. Browsers fall back to HTTP/1.1, so sites keep working, but pages with many small files can load a little slower. Turn HTTP/2 back on after you upgrade.

What the two bugs do

CVE-2026-123007 (CVSS v4.0 9.2) is a counting mistake in HTTP/2 flow control, the bookkeeping that limits how much data NGINX sends before the browser asks for more. When a request is cancelled while its data is still queued, NGINX gives the unused allowance back without checking the protocol's maximum. A visitor who keeps raising the allowance can push the counter past that ceiling. The size check then wraps around and NGINX copies memory it should never touch. Wiz Research, one of five teams that found these bugs, says it confirmed code execution on official 1.31.7 and 1.31.8 builds serving plain static files over HTTPS on 64-bit Linux, with no backend app and no third-party modules.

CVE-2026-123633 (CVSS v4.0 9.2) is a use-after-free. NGINX can close an HTTP/2 connection it thinks is idle while a request on that connection is still being forwarded to your app, and the request keeps using the freed memory. It only bites when NGINX is acting as a reverse proxy and its worker is running low on worker_connections, which an attacker can help along by opening many connections. It goes back to NGINX 1.19.7, from 2021.

F5's own advisories say code execution needs address randomization (ASLR) to be off or bypassed. Wiz says it bypassed ASLR in its tests, because the same bugs can be used to read memory first. So treat both as "a stranger can run code on the server", not as crash-only bugs.

Who is not in scope

  • NGINX with HTTP/2 off everywhere. Both HTTP/2 bugs need it on. A plain listen 443 ssl; with no http2 line on versions before 1.25.1 means HTTP/2 is off.
  • Sites where a CDN or load balancer in front ends the HTTP/2 connection and talks HTTP/1.1 to NGINX. Wiz notes that some CDNs and web application firewalls may block parts of the exploit, depending on how they forward traffic. That is a "maybe", not a fix, so upgrade the NGINX behind them anyway.
  • CVE-2026-123633 specifically needs NGINX proxying to a backend. A server that only serves files is still exposed to CVE-2026-123007.

What this is not

It is not a known attack yet. F5 reports no exploitation, neither bug is on CISA's Known Exploited Vulnerabilities catalog as of this writing, and Wiz says it will not publish its exploit for now. It is also not something you can fix in your own app code: the bug is in NGINX, so a well-written site behind a vulnerable NGINX is still exposed.

Don't wait for an exploited-in-the-wild label, though. Five research teams found the same flaws independently, and Wiz says AI tools helped it find and confirm them. The next people to look at this patch will have the same tools.

The rest of F5's November release

The same release fixes five more NGINX bugs. These only matter if you use the feature, and the same upgrade fixes all of them:

  • CVE-2026-121810 (9.2): use-after-free when HTTP/3 is on and the worker runs out of worker_connections.
  • CVE-2026-113425 (9.2): use-after-free in the mail proxy (mail {} blocks).
  • CVE-2026-123634 (9.2): use-after-free with the resolver directive, a proxied server name with variables, and SSI or mirror subrequests.
  • CVE-2026-125283 (6.9): a worker crash with try_files plus alias and certain map captures.
  • CVE-2026-118899 and CVE-2026-120967: a worker stuck reading a request body over SSL, and the stream module checking client certificates against the wrong server.

F5 also shipped critical fixes for BIG-IP, its load-balancer appliance. Five iRule bugs (CVE-2026-121805, CVE-2026-116953, CVE-2026-120292, CVE-2026-120285 and CVE-2026-120722, each CVSS v4.0 9.3) let an attacker crash the traffic engine and possibly run code when a virtual server uses an iRule with PEM::subscriber, GENERICMESSAGE::route, MR::message route, PSC::ip_address or DNS::scrape. CVE-2026-123637 (9.3) needs APM with a per-request policy that includes the Client Information and Endpoint Security agents. CVE-2026-120718 lets a stolen iControl REST token outlive its expiry. These touch BIG-IP 21.1, 17.5 and 17.1. Find the iRules that use those commands with tmsh list ltm rule one-line | grep -E 'PEM::subscriber|GENERICMESSAGE::route|MR::message|PSC::ip_address|DNS::scrape', and get the fixed builds from F5's advisories, starting with K000163946.

What do people ask about CVE-2026-123007?

Is my website affected if I use NGINX?

Probably, if NGINX is older than 1.30.7 or 1.31.9 and HTTP/2 is on, which is the common setup for HTTPS sites. Run nginx -v and nginx -T | grep http2 to check.

Is CVE-2026-123007 being exploited?

Not as of November 18, 2026. F5 reports no exploitation and the researchers have not released their exploit.

Does turning off HTTP/2 fix it?

It removes the attack path for both HTTP/2 bugs until you can upgrade. It does not fix the other bugs in the release, and you should turn HTTP/2 back on once you're on 1.30.7 or 1.31.9.

Do I need to do anything if I use a hosting company or CDN?

If they run NGINX for you, they have to patch it. If you run your own NGINX behind a CDN, upgrade it yourself.

Check if your agents touch this package with the HOL Guard evidence pack for CVE-2026-123007, or browse every tracked advisory in the HOL Guard CVE index.

References

All articles

Keep exploring

The engineering desk continues across the ecosystem: security research on shipping agents safely, and plugins that put the standards to work.