NGINX HTTP/2 Flaws Let Attackers Take Over Servers: Update Now
Share: https://www.ellixorlabs.com/blog/nginx-http2-flaws-cve-2026-123007-update-1-30-7 (copy URL for iMessage or social)
Published (display in IST)
Updated (IST)

Two critical HTTP/2 bugs in NGINX could let attackers run code on web servers without logging in. Here is how to check your version, what to update and how to stay safe if you cannot patch yet.
NGINX, the open source web server that sits in front of millions of websites and apps, released urgent updates on 18 November 2026 to fix two HTTP/2 flaws that researchers say let an attacker take over a server without logging in. The bugs, CVE-2026-123007 and CVE-2026-123633, are fixed in NGINX 1.30.7 (stable) and 1.31.9 (mainline), according to the official NGINX security advisories. Any business running NGINX with HTTP/2 switched on, whether on its own server or a cloud machine, should update or turn HTTP/2 off today. Wiz Research, one of several teams that found the bugs, rates both as critical, and the EU institutions' cyber security team, CERT-EU, said in its 18 November advisory that no attacks had been reported so far.
What are the NGINX HTTP/2 flaws and who found them?
Both bugs sit in the code NGINX uses to handle HTTP/2, the newer web protocol most browsers use to load pages over HTTPS. CVE-2026-123007 is memory corruption in HTTP/2 flow control, the mechanism that limits how much data each side can send, and it has been in NGINX since version 1.9.5 in 2015. CVE-2026-123633 is a use-after-free bug, where memory is released while a request still needs it; it affects version 1.19.7 onwards when NGINX acts as a reverse proxy and runs short of connection slots. Wiz says it used CVE-2026-123007 to run code on a test server that only served ordinary static files, so a site does not need a weak app behind NGINX to be at risk. Wiz gives both flaws a CVSS 4.0 score of 9.2, CERT-EU lists 8.1, and the NGINX page labels them major and medium respectively. Wiz, Xint, Rapid7, Ikotas Labs and Metnir found the bugs independently, and Wiz says it discovered both with its own AI code scanning tool. The same release fixes eight more bugs, including use-after-free flaws in HTTP/3, the DNS resolver and the mail proxy that CERT-EU says can also allow code execution in specific setups. Xint also reports a separate Linux kernel bug that it says can be chained with the NGINX flaws to gain full root control of a machine.
Is my website or app affected?
You are exposed if three things are true: you run NGINX open source between 1.9.5 and 1.31.8 or an affected NGINX Plus build, HTTP/2 is switched on, and attackers can reach the server, most obviously from the internet. Many businesses run NGINX without realising it, because it is a popular choice on Linux servers, in container images and in front of apps built with Node.js, Python or PHP. Wiz says NGINX powers more than 225 million websites. The catch is that Linux distribution packages are behind the official release. When we checked on the morning of 19 November (IST), Ubuntu's CVE tracker listed its nginx package as vulnerable on every supported release from 16.04 to 26.10, and Debian's security tracker showed a fix only in its unstable branch, with Debian 12 and 13 still vulnerable. If you installed NGINX with apt, a routine update may not protect you yet.
How do I fix it today?
Run nginx -v on each server to see the version, then nginx -T to print the full configuration and look for http2 on, or listen lines that include http2. If you can, upgrade to 1.30.7 or 1.31.9 using the official nginx.org packages or a rebuilt container image; NGINX Plus customers should apply the fixed builds in F5's advisory. If you are waiting on your distribution, turn HTTP/2 off as Wiz recommends, reload NGINX and switch it back on after patching. Browsers will fall back to HTTP/1.1, so your site stays up, though pages may load slightly slower. Then search your error log for lines saying a worker process exited on signal: CERT-EU says such crashes can indicate exploitation attempts, although they do not prove a break-in. This is the second critical HTTP/2 web server flaw in a week, after the Apache HTTP/2 bug we covered on 12 November, and Wiz argues that AI tools are making long hidden memory bugs far easier to find, which also shortens the gap between a fix and real attacks. As the Optimizely script attack showed, knowing exactly what software sits in front of your site, and who patches it, matters as much as the code you write.
Frequently asked questions
Which NGINX versions fix the HTTP/2 flaws? NGINX 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026, fix CVE-2026-123007 and CVE-2026-123633 along with eight other bugs. Open source versions from 1.9.5 to 1.31.8 are affected by at least one of the two HTTP/2 flaws. NGINX Plus customers should apply the fixed builds listed in F5's advisory.
Can I protect my website if I cannot update NGINX yet? Yes, as a stopgap. Wiz recommends turning HTTP/2 off: set http2 off; in affected server blocks on NGINX 1.25.1 or later, remove the http2 parameter from any listen directives, reload NGINX and confirm the old worker processes have exited. Switch HTTP/2 back on once you have upgraded.
Do I need to act if my website is on shared hosting or a managed platform? You usually cannot patch the server yourself, so ask your hosting provider whether its NGINX servers run 1.30.7 or 1.31.9, or have HTTP/2 switched off. If you rent your own virtual server or run your own containers, patching NGINX is normally your job, not the host's.
If you are not sure which servers sit in front of your website or apps, or who is responsible for keeping them patched, we can help you map that out and set up a sensible update routine. Get in touch with our team or see how we build and maintain web applications.
FAQ
Which NGINX versions fix the HTTP/2 flaws?
NGINX 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026, fix CVE-2026-123007 and CVE-2026-123633 along with eight other bugs. Open source versions from 1.9.5 to 1.31.8 are affected by at least one of the two HTTP/2 flaws. NGINX Plus customers should apply the fixed builds listed in F5's advisory.
Can I protect my website if I cannot update NGINX yet?
Yes, as a stopgap. Wiz recommends turning HTTP/2 off: set http2 off; in affected server blocks on NGINX 1.25.1 or later, remove the http2 parameter from any listen directives, reload NGINX and confirm the old worker processes have exited. Switch HTTP/2 back on once you have upgraded.
Do I need to act if my website is on shared hosting or a managed platform?
You usually cannot patch the server yourself, so ask your hosting provider whether its NGINX servers run 1.30.7 or 1.31.9, or have HTTP/2 switched off. If you rent your own virtual server or run your own containers, patching NGINX is normally your job, not the host's.
Talk to Ellixor Labs about this topic.
Source: NGINX (F5)