Nginx had a bad Wednesday. F5, which maintains the web server, pushed out fixes on November 18 for five bugs that each let an attacker run code on a server without logging in. All five carry a CVSS 4.0 score of 9.2. The oldest has been sitting in the HTTP/2 code since version 1.9.5, shipped in September 2015.
The story is less the bugs than who found them, and how fast.
An AI harness and 90 minutes
Xint, the autonomous security platform from Austin-based Theori, says it reported the set to F5 through HackerOne on October 16. Theori calls the collection “nginx2root”. One flaw, CVE-2026-123007, came from a human Xint researcher who was preparing for the ZeroDay Cloud 2026 competition. Theori then folded what he learned into the harness as a general feature, not something tuned for Nginx. A fully automated run went through about 50,000 lines of Nginx code in roughly 90 minutes and came back with the other four. No human guidance, according to CEO and cofounder Brian Pak. The models doing the reading were OpenAI’s, with Xint naming GPT 6.1 Sol and GPT-6 Luna.
Pak called the default-config HTTP/2 bug “the holy grail” for hackers of his generation. Hard to argue. Researchers have been reading this code for over a decade.
Wiz got there too
Here is the twist. Google-owned Wiz says it found the same serious flaws over the past month, separately. F5’s advisory credits Xint, Wiz, Rapid7 and Japan’s Ikotas Labs. Wiz bypassed ASLR and ran code on official 1.31.7 and 1.31.8 builds using HTTP/2 over TLS. Rapid7 put a proof of concept on GitHub, though it needs about 128 GB of HTTP/2 traffic and a fast link to work.
Several teams converging on the same decade-old bug in the same few weeks says a lot. These tools are now good enough that independent rediscovery is the normal outcome, not a coincidence. Xint also says Nginx’s advisory list logged 26 new vulnerabilities by November 17, against two in all of 2025.
The five flaws
- CVE-2026-123007: HTTP/2 enabled. The default-config one.
- CVE-2026-123633: HTTP/2 proxying to a backend while a worker runs low on connections.
- CVE-2026-123634: proxied server names built from variables, plus SSI or mirror subrequests.
- CVE-2026-121810: HTTP/3 enabled.
- CVE-2026-113425: Nginx running as a mail proxy.
Xint also found a separate Linux kernel bug in SCTP that turned worker-level code execution into host root in its tests, Docker included.
What to do
Upgrade open source Nginx to 1.31.9 or 1.30.7, which fix all five. NGINX Plus users need 37.3.0.1 or 37.0.8.1; R34 to R36 had no fix listed. Do a full restart or a binary upgrade. A reload keeps the old executable running. Turning off HTTP/2 only covers two of the five. Nobody has reported attacks yet, and the flaws were not in CISA’s KEV catalog at disclosure. Theori puts the exposed population at up to 11.8 million Nginx instances, its own estimate.
The market read
For F5 this is patch volume, and a lot of it. For the vendors selling AI bug hunting it is a showcase. Theori, Wiz (now inside Google) and Rapid7 all get their names on the same advisory. The harder question is the defender’s side. When bug discovery gets this cheap, the gap between finding and exploiting shrinks, and patch queues swell. That pressure is what start-ups like Anyday Security with ExploitTotal.ai and Corma are raising money against.