NGINX patches nginx2root, an 11-year-old HTTP/2 flaw that lets attackers run code
F5 released NGINX 1.31.9 and 1.30.7 on November 18 to fix five flaws, led by CVE-2026-123007, an HTTP/2 bug present since 2015 that researchers say lets attackers run code without logging in. No attacks have been reported yet.
Warden, covering security, outages and the rules for tech
, 3 min read
9.2CVSS 4.0 score of CVE-2026-123007, per Wiz
What to know
- CVE-2026-123007 affects every open-source NGINX release from 1.9.5 (2015) through 1.31.8 that has HTTP/2 turned on; the fixed versions are 1.31.9 and 1.30.7.
- Wiz, Xint, Rapid7, Ikotas Labs and Metnir found the HTTP/2 bugs independently; Wiz says it found both with an AI tool.
- As of November 18 no in-the-wild attacks had been reported and the flaw was not in CISA's Known Exploited Vulnerabilities catalog, though a public proof of concept exists.
F5 released new versions of NGINX, the open-source web server and reverse proxy, on November 18 to fix five security flaws. The most serious, CVE-2026-123007, is a bug in how NGINX handles HTTP/2 traffic that has been in the code since version 1.9.5 in September 2015. Researchers at Wiz and Xint say they used it to run their own code on servers without logging in. Xint has named the set of bugs "nginx2root."
The fixed releases are NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable). According to Wiz and The Hacker News, NGINX Plus customers get fixes in 37.3.0.1 and 37.0.8.1. The Hacker News reports that NGINX Plus R34 to R36 have no fix listed. We could not load F5's own advisory pages on nginx.org, so the version details here come from the researchers' posts and press reports.
What the bugs are
Wiz describes CVE-2026-123007 as an integer underflow in HTTP/2 flow control (the send_window value). A second HTTP/2 bug, CVE-2026-123633, is a use-after-free that has been present since 1.19.7. Wiz rates both critical, at 9.2 on the CVSS 4.0 scale, and says the second one is more likely to be exploitable when NGINX is set up as a proxy. For how those scores work, see our CVSS explainer.
The same release fixes three more flaws, according to Xint and The Hacker News: CVE-2026-123634, which needs a server name built from variables together with SSI or mirror subrequests; CVE-2026-121810, which needs HTTP/3 turned on; and CVE-2026-113425, which affects NGINX running as a mail proxy.
Code run through these bugs runs as an NGINX worker process, not as the administrator. The Hacker News reports that Xint reached full root access on a test host only by chaining a second, separate bug in the Linux kernel's SCTP code.
Who found it, and whether it is being used
Wiz says five teams found the HTTP/2 bugs independently: Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint. Wiz says its researchers found both with Atlas, its AI bug-hunting tool, and reported the use-after-free to F5 on October 21. Xint says it reported CVE-2026-123007 through HackerOne in mid-October.
"Two critical HTTP/2 flaws can allow attackers to compromise NGINX servers," Wiz wrote. It says it built working exploits but is not releasing them for now. A Rapid7 researcher has published a proof of concept on GitHub; The Hacker News says its notes limit it to a freshly started container on the same machine, and Cyber Kendra says it needs about 128 GB of HTTP/2 traffic. The Hacker News and Cyber Kendra both report that as of November 18 no vendor or researcher had seen the flaws used in real attacks, and none was in the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog.
How many servers
NGINX powers more than 225 million websites, Wiz says, citing Netcraft's September survey. Xint counted 56.7 million internet hosts identifying as NGINX on Shodan as of November 10; of the 11.94 million that showed a version number, 98.9% fell in the affected range. Xint notes those are version banners, not proof that a server is vulnerable.
Linux distributions had not all shipped fixed packages on November 18, Cyber Kendra reports, including Ubuntu and Red Hat Enterprise Linux. It also says the F5 NGINX Ingress Controller for Kubernetes is fixed in 5.8.0, while the separate community ingress-nginx project, which has been archived, will not get a fix.
Turning off HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633, according to The Hacker News, but not the other three flaws. Wiz says content delivery networks and web application firewalls that end HTTP/2 connections before they reach NGINX may partly shield servers behind them.
Why it matters
NGINX sits in front of a large share of the web, and a bug that lets an unauthenticated visitor run code on it is the kind attackers move on quickly once a working exploit spreads. This is the second widely deployed piece of server software this week, after Java4Shell, where researchers showed code execution before any attacks were seen. The gap between a patch and real attacks is often short; see our explainers on zero-days and how to read a security advisory.
Sources
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007, Wiz, November 18, 2026
- NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching, Xint, November 18, 2026
- 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers, The Hacker News, November 18, 2026
- nginx2root: NGINX HTTP/2 RCE Flaws (CVE-2026-123007) Patched, Cyber Kendra, November 18, 2026
Internet, outages and security
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.