Theori’s AI system, Xint, needed 90 minutes to find four of the five nginx flaws that F5 patched on 18th November, 2026. CVE-2026-123007, one of the five, had sat in nginx’s HTTP/2 code since 2015 and can let attackers run code without logging in.
What Happened?
- F5’s fixed releases, nginx 1.31.9 for mainline and 1.30.7 for stable, close all five flaws in one update.
- CVE-2026-123007 affects every open-source release from 1.9.5 through 1.31.8 and scores 9.2 under CVSS 4.0.
- Theori estimates that as many as 11.8 million nginx instances running vulnerable versions are active on the internet.
- F5, Wiz and Rapid7 had reported no real-world attacks exploiting CVE-2026-123007 by the time the fixes shipped.
A $1,000 model bill covered all five finds
Theori, a DARPA-backed US security firm, built Xint on OpenAI models to explore code, form hypotheses and verify them unaided. Co-founder and CEO Park Se-jun said Xint read about 50,000 lines of nginx code and “found four vulnerabilities without human help.” The fifth needed input from Theori’s researchers.
Park put the token bill for OpenAI’s GPT-6.1 Sol and GPT-6 Luna models at $1,000 across all five flaws. Xint’s team found them on 11th October and reported them to F5 through HackerOne five days later, so patches shipped 38 days after discovery.
Other teams got there too. Rapid7’s Stephen Fewer also found CVE-2026-123007 and contacted F5 a week before release, and Japan’s Ikotas Labs reported it independently. F5’s advisory credits Xint, Google-owned Wiz, Rapid7 and Ikotas Labs.
The pace shows in nginx’s own records. Its security advisories page now lists 36 entries carrying 2026 CVE IDs, against two with 2025 IDs. Old bugs keep surfacing in core open-source tools, as a 25-year-old curl bug showed in June.
Today, F5 released coordinated patches for two critical remote code execution flaws (CVE-2026-123633 and CVE-2026-123007) in NGINX, the open source web server powering over 225 million websites. Wiz Research (@wiz_io) paired Wiz Atlas with frontier models including Gemini 4 Carbon to uncover and validate the HTTP/2 bugs in parallel with other research teams, helping F5 ship fixes before attackers could strike.
— News from Google (@NewsFromGoogle) November 18, 2026
Working exploits still need specific conditions
F5 says attackers can run code where ASLR (address-space layout randomization) is off or can be bypassed. Wiz bypassed it in tests on official builds, and Xint said it needed nothing more than a reachable HTTP/2 port. Either way, the code runs with the nginx worker’s permissions.
Rapid7’s technical analysis puts the cost at about 128 GB of HTTP/2 data, and its demo exploit took two and a half minutes. Links slower than roughly 300 Mbit/s run past nginx’s default one-hour connection lifetime, and the attack fails. The method also relies on a glibc memcpy routine picked on x86-64 CPUs with avx512f and avx512vl support. Rapid7 said other routes may exist, but none are known yet.
Root takes a second bug. Xint chained worker access with a Linux kernel SCTP flaw dating to 2018 and reached host root, even from a Docker container. Containers share the host’s kernel, so the damage doesn’t stay boxed in.
Disabling HTTP/2 closes only two paths
Luxembourg’s CIRCL lists switching off HTTP/2 as a stopgap that helps reduce risk, but each flaw needs its own setup:
| CVE | Reachable when | Stopgap until upgrade |
|---|---|---|
| CVE-2026-123007 | HTTP/2 is on | Disable HTTP/2 |
| CVE-2026-123633 | HTTP/2 proxying while worker_connections run low | Disable HTTP/2 |
| CVE-2026-123634 | Variable-built proxied server name, plus SSI or mirror | Avoid that setup |
| CVE-2026-121810 | HTTP/3 is on | Disable HTTP/3 |
| CVE-2026-113425 | nginx runs as a mail proxy | Limit listeners to trusted networks |
What’s Next?
Admins already running nginx should:
- Upgrade to 1.31.9 or 1.30.7, or NGINX Plus 37.3.0.1 or 37.0.8.1. F5 lists no fix for Plus R34 to R36.
- Restart fully or use the live binary upgrade, because a plain reload leaves the old executable running.
- Check full distro package versions against the distribution’s advisory, since nginx -v may not reveal a backported fix.
- Block the SCTP module on hosts that don’t use it by adding “install sctp /bin/false” to a .conf file in /etc/modprobe.d/. That won’t unload a module already loaded.
The next move sits with the distros, since Ubuntu and Debian still listed nginx as vulnerable on release day. Until fixed builds land, stock-package users depend on upstream binaries or the official Docker images, which already carry 1.31.9 and 1.30.7 tags.
Park warned that AI speeds up both finding and exploiting flaws, so defenders can’t rely on people analyzing everything. When $1,000 in model fees surfaces a bug hidden since 2015, attackers can afford to scan wide, leaving patch speed as the main defense.




















































