Updated · 2 updates
NGINX HTTP/2 flaws let unauthenticated attackers run code; fixed versions released
Two flaws in the HTTP/2 support of NGINX, widely used web server software, can let an attacker run code on a server without logging in. Fixed versions are out, so administrators of servers with HTTP/2 enabled should update.
What's new
Added Xint Research's disclosure of five NGINX flaws, its kernel-bug chain to root, and reports that no exploitation has been seen. [1][2]
Added the second flaw, CVE-2026-123633 in NGINX Open Source, and the SANS Internet Storm Center's note that F5 patched five NGINX vulnerabilities. [3]
Newest coverage
- Help Net Security ·
NGINX2Root: F5 patches five critical NGINX vulnerabilities - BleepingComputer ·
Critical NGINX ‘NGINX2Root’ bugs let attackers hijack servers - Security Affairs ·
nginx2root:AI Discovers Five Critical nginx Flaws and a Path to Root - SANS Internet Storm Center StormCast ·
NGINX2ROOT HTTP/2 RCEs (CVE-2026-123007, CVE-2026-123633); Microsoft Agent Framework PyPI Compromise; Holiday Hack Challenge (Nov 19 2026)
Vulnerabilities
What happened
Rapid7 and F5, the company behind NGINX, disclosed CVE-2026-123007 on 18 November. Rapid7 describes it as an integer underflow (an arithmetic error in a counter) in NGINX's HTTP/2 handling. NGINX can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can exploit this by cancelling queued response data, which can lead to memory corruption and code execution in the worker process under certain conditions. [4][5]
NVD lists CVE-2026-123007 against NGINX Plus and a companion flaw, CVE-2026-123633, against NGINX Open Source; both are rated 9.2 on the CVSS v4 scale. Wiz analysed the two together as critical HTTP/2 flaws. The flaw dates to NGINX version 1.9.5, released on 22 September 2015. [4][6][5]
Five flaws, nginx2root
Xint Research disclosed five NGINX vulnerabilities under the name nginx2root, plus one Linux kernel bug, each with a working exploit. The researchers showed the NGINX flaws being chained with the kernel bug to gain root access. Rapid7, Wiz and three other research groups independently found and reported CVE-2026-123633 and CVE-2026-123007. [1][7][2]
Fixes and exploitation
F5 released fixed versions 1.31.9 and 1.30.7 on the day of disclosure. F5 patched five NGINX vulnerabilities in all, and CVE-2026-123007 needs no special configuration beyond HTTP/2 being enabled. [5][3]
CISA has not added either flaw to its list of flaws attackers are known to be using. Help Net Security reports there is no evidence any of the five has been exploited in the wild. [2][3]
Timeline
Update history
Added Xint Research's disclosure of five NGINX flaws, its kernel-bug chain to root, and reports that no exploitation has been seen. [1][2]
Added the second flaw, CVE-2026-123633 in NGINX Open Source, and the SANS Internet Storm Center's note that F5 patched five NGINX vulnerabilities. [3]
- First published
Explained
The technology and terms in this story. Learn more
- WeaknessMemory corruptionBugs that let a program write where it shouldn't in memory, often leading to code execution.
- ConceptCVSS · Common Vulnerability Scoring SystemA 0–10 score for how severe a vulnerability is in theory.
- ConceptCVE · Common Vulnerabilities and ExposuresThe public ID system for vulnerabilities, such as CVE-2026-12345, so everyone means the same bug.
- ConceptExploitCode or a technique that turns a software flaw into something an attacker can actually use.
Why it was possible
The weaknesses behind this story's CVEs, from each CVE Record.
- CWE-191Integer Underflow (Wrap or Wraparound)A subtraction goes below zero and wraps to a huge value, typically leading to an oversized copy.
- CWE-416Use After FreeThe program keeps using memory after releasing it, so an attacker who controls what lands there next can hijack execution.
- CWE-787Out-of-bounds WriteData is written outside the memory it belongs to; the most common root cause of exploited memory bugs.
Business ActionWhat this means inside your organization, and what to do about it, by company size.
Small business
No dedicated security staff; relies on providers
What to know
NGINX often runs behind hosting providers and websites; the risk applies to servers with HTTP/2 enabled. [5]
Mid-size company
A small IT or security team
Sources
- [1]Security Affairs · Nov 19, 09:21 UTC
nginx2root:AI Discovers Five Critical nginx Flaws and a Path to Rootcontext - [2]Help Net Security · Nov 19, 18:25 UTC
NGINX2Root: F5 patches five critical NGINX vulnerabilitiescontext - [3]SANS Internet Storm Center StormCast · Nov 19, 02:00 UTC
NGINX2ROOT HTTP/2 RCEs (CVE-2026-123007, CVE-2026-123633); Microsoft Agent Framework PyPI Compromise; Holiday Hack Challenge (Nov 19 2026)context - [4]Rapid7 Blog · Nov 18, 13:56 UTC
CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)context - [5]The Hacker News · Nov 18, 18:31 UTC
10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serverscontext - [6]Wiz Blog · Nov 18, 15:13 UTC
Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007context - [7]BleepingComputer · Nov 19, 14:57 UTC
Critical NGINX ‘NGINX2Root’ bugs let attackers hijack serverscontext