In 30 seconds

If you run NGINX with HTTP/2 turned on, today is patch day. Five critical vulnerabilities were disclosed on November 18, 2026, and the worst of them, CVE-2026-123007 nicknamed nginx2root, scores 9.2 out of 10 and can let an attacker run code on your server without ever logging in. Fixed versions 1.31.9 (mainline) and 1.30.7 (stable) are already out.10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serversthehackernews.com · rssOpen original sourceSee in source listFive Critical Vulnerabilities Found in World's Most Widely Used Open-Source Web Serverinfosecurity-magazine.com · rssOpen original sourceSee in source list
Researchers at Wiz say they demonstrated unauthenticated remote code execution on official NGINX 1.31.7 and 1.31.8 builds, bypassing ASLR, a core exploit mitigation, with no backend application involved. Separately, Xint researchers say they chained the bug with a Linux kernel flaw to escape Docker containers and reach root on the host. No active exploitation has been confirmed so far.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What happened
The story starts with a disclosure on November 18, 2026: two critical vulnerabilities, CVE-2026-123007 and CVE-2026-123633, both rated 9.2 under CVSS 4.0, affecting NGINX's HTTP/2 support. The root cause has been sitting in the open-source code since version 1.9.5, released on September 22, 2015, which makes this a genuine 10-year-old bug. F5, the company behind NGINX, shipped fixes the same day.The_Cyber_Newsx.com · The_Cyber_News · xOpen original sourceSee in source list10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serversthehackernews.com · rssOpen original sourceSee in source list
Both flaws require NGINX to accept HTTP/2 connections from clients, but their conditions differ. One affects certain reverse proxy setups, while the other can hit a server doing nothing more than serving static files. The flaws live in NGINX itself, not in the websites or APIs behind it.The_Cyber_Newsx.com · The_Cyber_News · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
The collection of five flaws, which Xint branded NGINX2Root, quickly drew demonstrations. Wiz researchers reported unauthenticated code execution on official builds with an ASLR bypass, and Xint reported chaining the NGINX bug with a separate kernel flaw for full root access. A public proof-of-concept also landed on GitHub, though it was demonstrated only in a constrained local Docker setup.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Why it matters
What makes this uncomfortable is how little it asks of the victim. HTTP/2 alone can expose an unpatched server: no vulnerable application code, no third-party module, nothing but the web server listening with the protocol enabled. Even servers hosting only static files are at risk.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listThe_Cyber_Newsx.com · The_Cyber_News · xOpen original sourceSee in source list
The blast radius is potentially huge. NGINX is described as the world's most widely used open-source web server, and Xint estimates roughly 11.8 million servers run versions inside the affected range.Five Critical Vulnerabilities Found in World's Most Widely Used Open-Source Web Serverinfosecurity-magazine.com · rssOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
ASLR was supposed to be a safety net here. The vendor advisory notes code execution is possible on systems where ASLR is disabled or where the attacker can bypass it, and Wiz researchers say they did exactly that on official builds. If a working bypass circulates, the distance from crash to code execution gets very short.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
What to do
First move: upgrade. NGINX 1.31.9 (mainline) and 1.30.7 (stable) contain the fixes, and both were released today. If you run NGINX Plus, check your version against F5's advisory, since both Plus and Open Source are in scope.bountywriteupsx.com · bountywriteups · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Patching will take some teams a while, so the documented workaround is to disable HTTP/2 entirely: set `http2 off;` in your server blocks or remove `http2` from your listen directives. It trades some performance for removing the attack surface.bountywriteupsx.com · bountywriteups · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Two follow-ups matter. A config reload alone will not replace the vulnerable binary, so make sure the new binary actually replaces the old one. And hunt your logs for unusual worker crashes and signs of command execution, since repeated worker segmentation faults are the signature of this bug being poked. If you containerize, remember that the kernel flaw in the Xint chain needs its own fix.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Confirmed and still uncertain
What is established: the flaw sits in HTTP/2 flow-control handling, can produce a heap buffer overflow and worker crashes, affects the data plane only with no control plane exposure, carries a CVSS 4.0 score of 9.2, and has patched releases available. A public proof-of-concept exists on GitHub.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listethiackx.com · ethiack · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
The PoC's real-world reach is contested, or at least narrowed. The Hacker News points out that the published code demonstrates exploitation in a constrained local Docker test setup, not a universal exploit against every NGINX deployment. Treat any 'every NGINX box is one click from root' framing with caution.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
What is not yet known: no active exploitation has been confirmed, versions past End of Technical Support were not evaluated, and exploitability across every configuration is still being characterized. Ethiack's research team says it is investigating the flaws and exploring a dedicated testing module.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source listethiackx.com · ethiack · xOpen original sourceSee in source list
What people are saying
Xint, the researchers behind the NGINX2Root name, say they chained the NGINX bug with a separate Linux kernel flaw and achieved remote code execution, a Docker container escape, and root on the host in their tests. They also put the exposure figure at about 11.8 million servers.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Wiz researchers say they confirmed unauthenticated remote code execution on official NGINX 1.31.7 and 1.31.8 builds, bypassed ASLR, and needed no backend application at all. Their demo is the strongest public signal so far that the flaw is practical rather than theoretical.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
The practitioner corner of X is already treating this as an all-hands update. Bountywriteups urged teams to patch reverse proxies and container images immediately, while The Hacker News told followers to verify HTTP/2 exposure and remember that a reload alone will not cut it.bountywriteupsx.com · bountywriteups · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Evolution
The bug's life began quietly: HTTP/2 flow-control code shipped in NGINX 1.9.5 on September 22, 2015, and the flaw hid there for about a decade before anyone flagged it.10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serversthehackernews.com · rssOpen original sourceSee in source listbountywriteupsx.com · bountywriteups · xOpen original sourceSee in source list
Then came a compressed sequence on November 18, 2026: disclosure of CVE-2026-123007 and CVE-2026-123633, same-day patched releases (1.31.9 and 1.30.7), a public PoC on GitHub, researcher demonstrations on official builds, and guidance to audit logs for worker crashes and command execution.The_Cyber_Newsx.com · The_Cyber_News · xOpen original sourceSee in source list10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serversthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Where things stand now: no confirmed active exploitation, but the ingredients for trouble, meaning a public PoC, a described ASLR bypass, and an enormous install base, are all in place. That combination is why the community tone has shifted from 'watch this' to 'patch now'.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Reach
9 independent groups, 13 updates, and 852 engagements.
Technical detail
Under the hood: the core bug is described as an integer underflow in HTTP/2 flow-control credit handling, triggerable purely through malicious WINDOW_UPDATE frames sent by the client. Per the F5-derived advisory, the flow-control window can exceed the allowed threshold, which can result in a heap buffer overflow typically followed by an NGINX worker segmentation fault.bountywriteupsx.com · bountywriteups · xOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Both headline CVEs are memory corruption issues rated 9.2 (Critical) under CVSS 4.0. The advisory notes that attackers can execute code on systems with ASLR disabled or when they can bypass ASLR, and stresses this is a data plane issue only, with no control plane exposure. Software versions past End of Technical Support were not evaluated.ethiackx.com · ethiack · xOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The escalation path is the chaining. Xint reports combining the NGINX RCE with a separate Linux kernel flaw to get code execution, escape a Docker container, and land root on the host. That kernel flaw requires its own fix, which NGINX 1.31.9 does not provide.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Sources and evidence
Primary reporting in this batch comes from The Hacker News and Infosecurity Magazine, with Cybersecurity News, dbugs, and Ethiack adding disclosure details. The dbugs entry carries the F5 advisory text covering NGINX Plus and NGINX Open Source, including the flow-control and ASLR conditions.10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serversthehackernews.com · rssOpen original sourceSee in source listFive Critical Vulnerabilities Found in World's Most Widely Used Open-Source Web Serverinfosecurity-magazine.com · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Artifacts exist for anyone who wants to verify: a public PoC repository on GitHub (sfewer-r7/CVE-2026-123007), a dedicated site at nginx2root.com, and a dbugs tracking page (PT-2026-150614). The standing caveat: the PoC was demonstrated in a local Docker setup, not as a universal exploit.github.comgithub.com · rssOpen original sourceSee in source listnginx2root.comnginx2root.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Confidence picture: patch availability, CVSS scores, and the advisory mechanics are well corroborated across sources. The Wiz demonstration, the Xint kernel chain, and the 11.8 million server estimate circulate via posts and summaries rather than full writeups in this batch, so the most dramatic impact claims should be read as strong allegations pending the primary research.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Sources
- 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serversthehackernews.com · rss
- Five Critical Vulnerabilities Found in World's Most Widely Used Open-Source Web Serverinfosecurity-magazine.com · rss
- TheHackersNewsx.com · TheHackersNews · x
- TheHackersNewsx.com · TheHackersNews · x
- DarkWebInformerx.com · DarkWebInformer · x
- The_Cyber_Newsx.com · The_Cyber_News · x
- TheHackersNewsx.com · TheHackersNews · x
- TheHackersNewsx.com · TheHackersNews · x
- ptdbugsx.com · ptdbugs · x
- bountywriteupsx.com · bountywriteups · x
- TheHackersNewsx.com · TheHackersNews · x
- ethiackx.com · ethiack · x
- github.comgithub.com · rss
- nginx2root.comnginx2root.com · rss



