On 18 November 2026 Wiz Research published details of two critical remote code execution bugs in nginx, alongside F5's security release. The post, "Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007" by Nir Ohfeld and Tomer Schwartz, opens like this:
"Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered two critical remote code execution vulnerabilities in NGINX, software used to receive and route traffic to production applications and APIs."
"The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2."
Most retellings will stop there. The useful part is the next sentence, because it tells you whether you are exposed at all:
"Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server."
This is a follow-up to The nginx Kill Chain: Three CVEs, One Root Shell from May. Those were different bugs in different parts of nginx. This time everything turns on one protocol setting.
Two bugs, two different sets of conditions
Both need HTTP/2. Beyond that they are not the same, and treating them as one bug gets the risk wrong in both directions.
CVE-2026-123007: the broad one. An integer underflow in HTTP/2 flow control. Wiz's table describes it as "Exploitable in default configurations with HTTP/2 enabled" and lists affected versions as 1.9.5 to 1.31.8, so the bug dates back to 2015. It does not need an application behind nginx:
"Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules."
Wiz says it confirmed remote code execution with an ASLR bypass on official 1.31.7 and 1.31.8 builds, using HTTP/2 over TLS on 64-bit systems.
CVE-2026-123633: the proxy one. A use-after-free on HTTP/2 connections. The table describes it as "Exploitable configured with HTTP/2 as a proxy server", with affected versions 1.19.7 to 1.31.8. Wiz's write-up adds a further condition: it bites when nginx is forwarding requests to an upstream and its free connection slots run low. A plain static-file server is not the case this one describes.
On both, Wiz warns that the usual memory-safety defences are not enough on their own: "Typical memory safety mitigations such as ASLR do not protect against these issues, as attackers can use either vulnerabilities for memory read access prior to code execution."
The post does not report exploitation in the wild, and Wiz is not publishing its exploits: "In the interest of customer protection, we will not be releasing these exploits at this time." Neither of those is a reason to wait.
What to upgrade to
The fixed releases, as Wiz lists them:
- nginx open source: 1.30.7 (stable) or 1.31.9 (mainline). Both fix both CVEs.
- NGINX Plus: the fixed builds differ per CVE. 37.0.7.1 and 37.2.0.1 fix CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 fix CVE-2026-123007. Check the CVE you care about against the build you run, not one pair of numbers for both.
The same release fixes several other nginx CVEs, including bugs in the HTTP/3 proxy, the DNS resolver and the mail proxy. If you run any of those features, read F5's advisory for their conditions too.
If you install nginx from your distribution, the version string will not tell you. Distributions backport fixes into their own package versions, so nginx -v printing 1.24.0 says nothing either way. What tells you is the package changelog. On Debian and Ubuntu:
apt-get changelog nginx | grep -E "CVE-2026-123007|CVE-2026-123633"
No output means your installed package does not mention either fix. When we checked on 19 November 2026, Ubuntu 24.04's newest nginx package was dated 24 October and named neither CVE.
The stopgap, both halves of it
If you cannot upgrade tonight, Wiz's advice is to turn HTTP/2 off: "If you cannot upgrade immediately, temporarily disable HTTP/2 on affected NGINX instances:" The instruction that follows has two parts, and the second is the one people miss. Set http2 off; in affected server blocks on nginx 1.25.1 or later, and remove the http2 parameter from any listen directives.
# before
listen 443 ssl http2;
# after (nginx 1.25.1 and later can also use: http2 off;)
listen 443 ssl;
Two practical notes from doing this on our own servers:
- Older nginx has no
http2 off;directive. It was added in 1.25.1. On anything older, removinghttp2from thelistenlines is the whole change. HTTP/2 is set per address and port, so it has to come off everylistenline on that port, not just the one site you are worried about.nginx -T | grep http2shows what is still on. - A reload is not the end of it. Wiz says to "confirm the old workers have exited", and this matters. After a reload, the old worker processes keep serving the connections they already hold until those close. Without
worker_shutdown_timeoutset, that can be a long time. When we reloaded, eight old workers were still running a minute later, and with no timeout set they would have kept running for as long as their connections stayed open.ps --ppid $(cat /run/nginx.pid) -o pid,cmdlists them as "shutting down". Settingworker_shutdown_timeout 30s;in the main context bounds this for future reloads.
Then check what clients are actually offered:
echo | openssl s_client -connect your.host:443 -servername your.host -alpn h2 2>/dev/null | grep -i alpn
If HTTP/2 is off, you will not see h2. Re-enable HTTP/2 once you are on a fixed build.
Wiz also flags signs worth a look in your logs: unexpected nginx worker crashes, or commands launched by nginx. It is careful to call these "general warning signs, not confirmed indicators".
On CDNs and WAFs the post is deliberately hedged: "CDNs and WAFs that terminate HTTP/2 may mitigate parts of the exploit by not reflecting the exact payload back to the underlying NGINX server. This depends on implementation." A CDN in front of you is not a reason to skip the upgrade.
What we did on DeployBase
Our own front door is nginx from Ubuntu's packages. It had HTTP/2 enabled for deploybase.io and every address under *.deploybase.io, and it proxies to the services behind it, so it met the conditions for both CVEs. With no fixed Ubuntu package yet, we took the stopgap above on 19 November 2026: HTTP/2 is off on that nginx, the old workers were confirmed gone, and worker_shutdown_timeout is now set. Those addresses now offer HTTP/1.1 only. We will turn HTTP/2 back on when the package changelog names both fixes.
Customer sites on their own custom domains are routed by Traefik, which is not nginx and is not affected by these CVEs, so those still use HTTP/2. If your app runs its own nginx inside its container, that nginx receives requests over HTTP/1.1 from the proxy in front of it, so the HTTP/2 precondition is not met there. It is still worth updating its image when fixed builds reach it.
Source, read 19 November 2026: Wiz Research, "Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007" (18 November 2026). Version and package details for our own servers were read from their configuration and package manager on the same day.