NGINX2Root: two critical flaws patched — one sat in NGINX code for a decade
F5 fixed two critical unauthenticated remote-code-execution flaws in NGINX's HTTP/2 code on November 18, one of them present since 2015. No exploitation in the wild had been reported, but a public proof of concept is circulating.
📊 Scorecard: our Bearish call on $FFIV is a hit so far: from $321.04 to $318.09 at the latest close (-0.9%). Against QQQ the call is wrong: the stock is 1.3 points ahead of the index.

The News
F5 released security updates on November 18 fixing ten vulnerabilities in NGINX, the web server software that powers a huge share of the internet. Five of them, collectively called NGINX2Root, are memory-safety flaws that can lead to unauthenticated remote code execution. Headlining the release are two critical unauthenticated remote-code-execution vulnerabilities in HTTP/2, both rated 9.2 out of 10 under CVSS 4.0 (8.1 under CVSS 3.1): CVE-2026-123007 and CVE-2026-123633.
The first flaw, CVE-2026-123007, is a flow-control integer underflow — a counting error in how NGINX tracks data flow — present since NGINX version 1.9.5, released in 2015. Researchers at Wiz demonstrated it as full remote code execution on a server serving only static files, meaning even a simple website with no login or database could be taken over. The second, CVE-2026-123633, is a use-after-free flaw in HTTP/2 connection handling, present since version 1.19.7 from 2021. In plain language, the software kept using a piece of memory after it had been freed, which an attacker can exploit to run their own code.
The two HTTP/2 flaws were found independently by five research teams: Wiz, Ikotas Labs, Metnir, Rapid7 and Xint. Xint reported all five of the NGINX2Root flaws and gave the set its name. Both are fixed in NGINX Open Source 1.30.7, the stable release, and 1.31.9, the mainline release; NGINX Plus users need 37.0.8.1 or 37.3.0.1. Builds 37.0.7.1 and 37.2.0.1 fix only CVE-2026-123633, and Plus releases R33 to R36 get no fix. F5 says code execution requires ASLR — a standard defence that randomises where programs sit in memory — to be switched off or bypassed, but researchers demonstrated an ASLR bypass in the lab.
No exploitation in the wild had been reported as of November 18, and none of the five flaws is on CISA's Known Exploited Vulnerabilities catalog. But a public proof of concept is circulating — Rapid7 published a full unauthenticated RCE exploit for CVE-2026-123007 on GitHub on disclosure day — which shortens the window before someone tries. It is heavily constrained, needing roughly 128 GB of HTTP/2 traffic over one connection and a specific glibc memory-copy routine, and Wiz is not releasing its own exploits. The retired ingress-nginx controller will not receive a fix. HTTP/2 is off by default in NGINX, so exposure requires it to be explicitly enabled. F5 shares closed Wednesday at $321.04, up 5.21%.
A decade-old bug in the web's plumbing got fixed in a day — the race now is patching before someone uses it.
Why It Matters
The flaws matter because of what they allow and how long they hid. Remote code execution is the most serious class of bug: an attacker who does not even need to log in can run commands on the server. One of these flaws has been present since 2015 — a decade of NGINX releases carried it. The Wiz demonstration is the key detail: they showed takeover on a server serving only static files, the simplest possible website, which means the attack surface is enormous.
The discovery pattern matters too. Five independent research teams — Wiz, Ikotas Labs, Metnir, Rapid7 and Xint — found these flaws separately, which suggests the bugs were findable by anyone looking carefully. When a flaw is found by five teams at once, it is a safe bet that others, including attackers, are looking too. The public proof of concept shortens the fuse further.
The exposure is narrower than the headlines suggest, and that is worth saying plainly. HTTP/2 is switched off by default in NGINX, so only servers where an operator deliberately enabled it are at risk. F5 also notes that exploitation requires ASLR, a standard defence, to be off or bypassed — though researchers demonstrated a bypass in the lab, so that is not a wall, just a hurdle. The retired ingress-nginx controller will never be fixed, so organisations still running it need to migrate rather than wait for a patch.
Analyst's Take
Our call is Bearish. Two critical remote-code-execution flaws, one of them sitting in the code for a decade, is bad news for the internet's infrastructure — even if no attack has been seen yet. NGINX runs a large share of the world's websites, and the Wiz demonstration matters: full takeover of a server that only serves static files means the bar for victims is very low. Any site with HTTP/2 switched on and an unpatched version is exposed.
The mitigating facts are real. HTTP/2 is off by default, so many servers are not exposed at all. Exploitation requires bypassing ASLR, a standard memory defence, though researchers have shown that bypass working in the lab. No exploitation in the wild had been reported as of November 18, and nothing is on CISA's exploited list. But a public proof of concept is circulating, and history says the gap between a public proof of concept and real attacks is measured in days, not months.
The F5 share move — up 5.21% to $321.04 on Wednesday — is about the wider market, not this disclosure; the stock rose with a strong day for security names ahead of Palo Alto's post-market results that evening. What to watch is patching speed: whether operators upgrade to 1.30.7 or 1.31.9 quickly, and whether CISA adds either flaw to its exploited list. The retired ingress-nginx controller gets no fix at all, so its users need to move. Reader poll: Has your team patched NGINX yet? Vote: Patched, Patching now, Not using NGINX.
Are you bullish or bearish on this story?
By The Numbers
FAQ
What is remote code execution?
Remote code execution, or RCE, is a flaw that lets an attacker run their own commands on a server over the internet, without logging in. It is one of the most serious kinds of bug, because it can turn a web server into a machine the attacker controls — to steal data, install malware or attack other systems.
What is HTTP/2?
HTTP/2 is a newer version of the protocol web browsers and servers use to talk to each other. It is faster than the older version, but it is switched off by default in NGINX Open Source, so a server is only exposed if its operator deliberately turned HTTP/2 on. The exception is the ingress-nginx controller, which serves HTTP/2 by default — and it will never receive a fix.
What is a CVSS score?
CVSS is a standard 0-to-10 rating of how severe a security flaw is. A score of 9.2, which both of these flaws received, counts as critical — the top band. It reflects how easily the flaw can be used and how much damage it can do.
👁
Source: Cycode