Security ·
nginx CVE-2026-123007: critical HTTP/2 flaw allows unauthenticated code execution
On 18 November 2026 the nginx project released versions 1.30.7 and 1.31.9, which fix the critical HTTP/2 flaw CVE-2026-123007. Anyone can attack an exposed server without logging in, so update and restart now.
The nginx web server sits in front of a large share of e-shops, company sites and applications, often as a reverse proxy for WordPress or a custom backend. On 18 November 2026 the project released 1.30.7 (stable) and 1.31.9 (mainline), fixing CVE-2026-123007. Security vendors describe an integer underflow in HTTP/2 flow control that corrupts memory and can be exploited for remote code execution without any login. The CVSS 4.0 score is 9.2.
The bug has been in the code for about ten years. Affected are nginx Open Source versions from 1.9.5 through 1.30.6 and from 1.31.0 through 1.31.8. The same release fixes a second HTTP/2 flaw, CVE-2026-123633 (use-after-free), which matters when nginx runs as a proxy. In total the release closes five vulnerabilities, collectively called NGINX2Root. Public exploit code is reported to exist, so waiting another day is a real risk. Only servers with HTTP/2 enabled are exposed, which is the default on most HTTPS sites today.
What if you cannot update right away? The temporary workaround is to disable HTTP/2, by removing the http2 parameter from the listen directive or setting http2 off. That blocks both HTTP/2 bugs but not the other three fixed in the same release. The fixed versions must be installed and nginx restarted, because a reload leaves the old processes running. If you get nginx from Debian or Ubuntu packages, wait for your distribution's patched package or use the official nginx repository. For NGINX Plus, follow the F5 advisory.
Unlike many critical bugs, this one hits infrastructure rather than a single application. Anything behind nginx can be affected, including the internal AI tools and chatbot APIs many companies have exposed to the internet in recent months. We have not seen reports of mass exploitation in the wild at the time of writing, but with public exploit code that is a matter of days.
What it means for companies
Find out where nginx runs in your company: on hosting, in containers, on load balancers and at suppliers who operate your site. Update to 1.30.7 or 1.31.9, restart the service and confirm the version with nginx -v. If that is not possible today, disable HTTP/2. Routine patching and monitoring is what website maintenance and EU hosting cover, and a wider exposure review belongs to cyber security. Prahapp, the AI division of Buinsoft Technology in Prague, can also review the servers that run your AI agents.
Sources: Wiz: Unauthenticated Remote Code Execution in NGINX (CVE-2026-123633 and CVE-2026-123007), The Hacker News: 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers