Key takeaways
- F5 fixed eight Nginx vulnerabilities on November 18, 2026, in nginx 1.30.7 and 1.31.9.
- CVE-2026-123007, a memory-corruption bug in HTTP/2 present since version 1.9.5, lets an unauthenticated attacker run code on the server.
- Wiz and Xint say AI tools found most of the bugs, and no working exploit has been released.
F5 patched eight flaws in Nginx on November 18. The worst Nginx vulnerability is a memory-corruption bug in HTTP/2 that lets an attacker run code on a server without logging in. The fixed releases are nginx 1.30.7 and 1.31.9. At least five teams found the flaws independently, and two of them, Wiz and Xint, say AI tools did much of the finding.
Nginx is the web server and reverse proxy in front of a large share of the internet's sites and APIs. A bug that needs no password and works with a common setting, HTTP/2 turned on, is about as bad as server bugs get. The flaw behind the worst of them has been in the code since version 1.9.5, released in 2015.
Which Nginx vulnerabilities were fixed
The nginx.org advisories page lists eight issues fixed in 1.31.9, and seven of them in 1.30.7 too. The ones that matter most:
| CVE | What it is | Nginx rating | Vulnerable versions |
|---|---|---|---|
| CVE-2026-123007 | Memory corruption in HTTP/2 flow control | Major | 1.9.5 to 1.31.8 |
| CVE-2026-123633 | Use-after-free in HTTP/2 | Medium | 1.19.7 to 1.31.8 |
| CVE-2026-121810 | Use-after-free in HTTP/3 | Medium | 1.25.0 to 1.31.8 |
| CVE-2026-123634 | Use-after-free in the resolver | Medium | 0.6.18 to 1.31.8 |
| CVE-2026-113425 | Use-after-free in the mail proxy | Major | 0.5.33 to 1.31.8 |
| CVE-2026-118899 | Infinite loop reading a request body over TLS 1.3 | Major | 1.13.0 to 1.31.8 |
Nginx's own ratings are lower than the researchers'. Wiz scores both HTTP/2 bugs 9.2 out of 10 on CVSS 4.0, the standard severity scale, and calls them critical. For Nginx Plus, F5's paid version, Wiz lists fixes in 37.0.7.1, 37.0.8.1, 37.2.0.1 and 37.3.0.1, depending on the CVE.
How bad the HTTP/2 bug is
Wiz says CVE-2026-123007 works on a plain setup: Nginx serving static files over HTTPS with HTTP/2 on, on a 64-bit system. No login is needed. Wiz also says ASLR, the memory randomization that usually makes such bugs hard to exploit, doesn't stop it, because the flaw can leak memory first.
Xint's write-up calls it the most serious of the five it reported. An attacker can run commands with the rights of the Nginx worker process. Xint also chained an Nginx bug with an unpatched flaw in the Linux kernel's SCTP networking code to get root on the host, and in its tests that worked from inside a Docker container. It is holding back most details of the kernel bug until there is a fix.
Neither company has released a working exploit, and Wiz reports no attacks in the wild so far.
AI found these bugs
Wiz says its AI code-scanning harness, Wiz Atlas, found both HTTP/2 bugs, and that its researchers used Google and OpenAI models to confirm the impact. Xint says one of its researchers found CVE-2026-123007 and a fully automated Xint scan found the other four. "AI-assisted research is finding bugs faster than ever, even in code as heavily studied as nginx," Xint wrote.
It is the second such disclosure this week, after Java4Shell, an AI-found flaw in Java's standard library. Old, widely read code is getting a fresh audit from machines, and the patches are arriving in bunches.
What to do
Upgrade to nginx 1.30.7 or 1.31.9. Xint warns that Linux distribution packages may carry the fixes without changing the version number nginx -v prints, so check your distribution's security notice rather than the number alone.
If you can't upgrade yet, Wiz suggests turning HTTP/2 off: set http2 off; in the affected server blocks on Nginx 1.25.1 or later, remove the http2 parameter from listen lines, reload, and make sure old workers have exited. A CDN or firewall that ends HTTP/2 connections in front of Nginx may reduce exposure. Xint suggests blocking the kernel's SCTP module on hosts that don't need it.
Watch for the kernel fix for Xint's SCTP bug, and for exploits once attackers compare the old and new code.



