Threat researchCisent
NGINX: a ten-year-old HTTP/2 flaw lets attackers run code without logging in
NGINX fixed a flaw that has been in its HTTP/2 support since 2015 and lets attackers run code on the server without credentials; no attacks exploiting it are known yet.

On November 18, NGINX released version 1.31.9, which fixes CVE-2026-123007, a flaw in HTTP/2 flow control reported by the research firm Xint.1 The stable branch was fixed in 1.30.7.2 The flaw has been in NGINX’s code since version 1.9.5, from 2015, and Xint disclosed it along with four others under the name NGINX2ROOT.3
What fails
- It affects every NGINX installation with HTTP/2 enabled, from version 1.9.5 to 1.31.8.2 It requires neither credentials nor administrator access.3
- According to F5, the company behind NGINX, an attacker can run code where ASLR, the protection that randomizes memory addresses, is turned off or can be bypassed.4 The researchers documented how to bypass it, so CIRCL, Luxembourg’s incident response center, warns that ASLR is no substitute for the patch.3
- The code runs with the permissions of an NGINX worker process. Getting root takes another flaw: Xint chained it with one in the Linux kernel, in SCTP, even with NGINX running inside a Docker container.3
- The other four flaws depend on more specific features, such as HTTP/3, the resolver or the mail proxy.3 NGINX Plus is affected too.4
How serious it is
- F5 scores it 9.2 out of 10 on the CVSS 4.0 scale, and 8.1 on version 3.1.5
- As of November 18, neither F5 nor the researchers at Wiz and Rapid7 had reported attacks, and the flaw was not in CISA’s catalog of exploited vulnerabilities.4
- Proof-of-concept code is public, although its notes say it only works to demonstrate the attack against a freshly started Docker container on the same machine.4
What to do
- Update to NGINX 1.31.9 or 1.30.7.2 If you use your Linux distribution’s NGINX, install the distribution’s update as soon as it is available.3
- Restart the service after updating: a reload doesn’t replace the running executable, and old connections can stay on the old workers.3
- Until you can update, turning off HTTP/2 blocks the known path to this flaw, with
http2 off;from version 1.25.1 on. Keep in mind that gRPC and other applications need it, and that this doesn’t cover the other four flaws.3 - Keep ASLR enabled and check that nobody has turned it off.3
- On machines that don’t use SCTP, block its module from loading automatically until a kernel patch is available.3
Where Cisent comes in
NGINX usually sits at the edge of the network, in front of everything else. An old version on a server nobody checks is exactly what an attacker looks for.
Sentinel Red Team attacks the organization’s systems with its authorization and within the scope it defines, to find the gaps before an attacker does: the admin panel exposed on a server nobody watches, the service published by mistake, the insecure configuration. It’s ongoing testing, not one audit a year, and every new attack pattern helps train the defense.
Sources
NGINX, “Changes with nginx 1.31.9”, November 18, 2026. https://nginx.org/en/CHANGES↩︎
NGINX, “nginx security advisories”, CVE-2026-123007 entry. https://nginx.org/en/security_advisories.html↩︎
CIRCL, “TR-105 NGINX2ROOT - Remote Code Execution in NGINX and Potential Host Compromise”, November 2026. https://www.circl.lu/pub/tr-105/↩︎
Swati Khandelwal, “10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers”, The Hacker News, November 18, 2026. https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html↩︎
CVE Program, CVE-2026-123007 record, published by F5 on November 18, 2026. https://www.cve.org/CVERecord?id=CVE-2026-123007↩︎