Change language to
0:00

Nginx has patched a decade-old HTTP/2 flaw that AI-assisted researchers showed could let an unauthenticated attacker run commands on the web server.

Administrators should update to Nginx 1.31.9 or 1.30.7. F5 recommends disabling HTTP/2 on affected ports if an immediate update isn’t possible, but that leaves other flaws unpatched and can break services such as native gRPC.

The Nginx security advisories list CVE-2026-123007 as ‘major’, though researchers describe it as critical. The memory-corruption bug dates back to Nginx 1.9.5, which added HTTP/2 support in 2015. Xint.io demonstrated command execution with the privileges of an Nginx worker process.

Researchers built working exploits. According to CSO Online, the US Cybersecurity and Infrastructure Security Agency’s assessment found no exploitation of either flaw in the wild yet. WatchTowr’s Yordan Ganchev cautions that the flaw isn’t straightforward to exploit. He says vulnerable systems must be directly exposed to the internet, with no web application firewall or CDN terminating HTTP/2. Nginx is estimated to power about a third of the internet. Shodan lists 56.7 million hosts running it, and 98.9% of those that disclose a version report one in the vulnerable range.

Subscribe to our Newsletters for more Tech Stories

Which Nginx versions should you patch?

VulnerabilityF5 severityVulnerable range listed by NginxFixed releases
CVE-2026-123007: HTTP/2 flow-control memory corruptionMajor1.9.5–1.31.81.31.9 and 1.30.7
CVE-2026-123633: HTTP/2 use-after-free (Drainbreak)Medium1.19.7–1.31.81.31.9 and 1.30.7
CVE-2026-123634: resolver flawMedium0.6.18–1.31.81.31.9 and 1.30.7

The releases fix ten issues in all. Those include a medium-rated HTTP/3 flaw and two major-rated bugs: an infinite loop when reading TLS 1.3 request bodies and a flaw in the mail proxy. The batch also includes fixes involving PROXY protocol v2, try_files aliases, stream SNI, and ssl_preread.

Disabling HTTP/2 blocks both HTTP/2 flaws, but it doesn’t address the resolver, HTTP/3, or mail proxy bugs. Nginx Plus users should update to 37.3.0.1 on the newer release line or 37.0.8.1 on the 37.0 line. Releases R33 through R36 are out of technical support and won’t receive fixes.

Miggo Security CEO Daniel Shechter warns that Linux distributions can backport a fix without changing the Nginx version number, so check whether your distribution’s package includes the patch. A configuration reload doesn’t replace the running code, so verify that the running service is using the updated binary. Shechter also cautions that access logs and web application firewalls can miss HTTP/2 attacks.

How AI helped find the bugs

Rapid7, Wiz, Xint, and Ikotas Labs reported CVE-2026-123007 to F5. Metnir, Wiz, and Xint found Drainbreak. Rapid7 senior principal security researcher Stephen Fewer didn’t mention AI in his write-up, while the other four teams used AI agents or testing frameworks.

Xint’s autonomous testing framework found five of the flaws. CEO Brian Pak said it scanned “50,000 lines of code in just 90 minutes”. He described the flaw it found as critical because it gave unauthenticated users a path to remote code execution.

The team also found a separate Linux kernel flaw that can raise the impact to root access. The kernel bug doesn’t have a CVE or a patch yet, and Xint is withholding details. The Nginx updates don’t fix the kernel bug. Until a kernel patch ships, administrators who don’t use SCTP can block the module from loading by adding install sctp /bin/false to a file under /etc/modprobe.d.

AI-assisted bug hunting has also turned up flaws in Windows and Firefox. The PHP2shell fix followed the same pattern: apply the patch, then confirm the running service uses the patched code.