Emergency NGINX Patches Fix Critical Remote Code Execution Flaws Found with AI
F5 has issued out-of-band security fixes for 10 vulnerabilities in open source NGINX, the web server that handles traffic for about a third of all websites (around 225 million). Two of the flaws are critical and allow a remote attacker to execute code on the server without logging in. F5 says it has found no evidence of active exploitation in the wild.
The two critical bugs, CVE-2026-123633 and CVE-2026-123007, both carry a 9.2 CVSS rating and both require HTTP/2 to be enabled. Wiz researchers describe them as memory-safety problems in how NGINX handles HTTP/2 traffic. One is a use-after-free, where memory is released while a request still needs it. The other is an invalid memory copy caused by incorrect flow-control accounting. CVE-2026-123007 affects versions dating back to NGINX 1.9.5 in 2015, so it sat in the code for around a decade.
Researchers at Wiz, Ikotas Labs, Metnir, Rapid7 and Xint each found at least one of the two bugs independently, most with AI assistance. Rapid7 published a proof-of-concept against NGINX 1.31.8 in a Docker image. Xint found three other NGINX flaws plus a Linux kernel bug that can be chained with any of five NGINX issues to gain root on the host. It calls the set "nginx2root" and has shown attacks working on major clouds and bare-metal servers.
The disclosure follows recent AI-found flaws in PHP, Apache and Java. Wiz's Tomer Schwartz says defenders should treat every internet-connected system as potentially vulnerable, and notes that finding affected versions, testing patches and rolling out mitigations still takes heavy manual effort. F5 advises anyone running NGINX to update to 1.31.9 as soon as possible.
Why it matters
Public proof-of-concept code and demonstrated root escalation mean the gap between disclosure and attack may be short, even though F5 sees no exploitation yet. Any business with NGINX facing the internet, including inside containers or cloud hosts, can no longer assume a long-standing, stable component is safe. The pace of AI-driven discoveries also forces teams to know exactly where NGINX runs and which settings are enabled, because manual inventory is now the bottleneck.
What to do
- Update open source NGINX to version 1.31.9.
- Identify every NGINX server that has HTTP/2 enabled, since both critical flaws need it.
- Disable HTTP/2 as an interim mitigation where patching cannot happen immediately.
- Review internet-facing hosts running versions back to 1.9.5 for exposure.