NGINX nginx2root: five unauthenticated memory-corruption flaws (CVE-2026-123007 and CVE-2026-123633 in HTTP/2, CVE-2026-121810 in HTTP/3, CVE-2026-123634 in the resolver, CVE-2026-113425 in the mail proxy) can lead to code execution as the worker process; fixed in nginx 1.31.9 and 1.30.7 and NGINX Plus 37.3.0.1 and 37.0.8.1, Rapid7 proof of concept public, no exploitation reported (CVSS 4.0 9.2)
NGINX nginx2root: five unauthenticated flaws reach worker RCE, Rapid7 PoC public; update 1.31.9, 1.30.7 or Plus 37.3.0.1
Defender actions
- Update every internet-facing nginx to 1.31.9 or 1.30.7 (NGINX Plus to 37.3.0.1 or 37.0.8.1) and restart the process, because a reload does not replace the running executable; where the update waits, disable HTTP/2 on exposed listeners, which blocks only CVE-2026-123007 and CVE-2026-123633, since five unauthenticated flaws reach code execution as the worker and Rapid7's proof of concept for one of them is public.
Analysis
F5 and the nginx project published the nginx2root fixes (nginx.org, 2026-11-18); CERT-EU counts five vulnerabilities, all able to lead to unauthenticated code execution with the privileges of the NGINX worker process (CERT-EU, 2026-11-18). CVE-2026-123007 is an HTTP/2 flow-control overflow: cancelling queued response data makes nginx use an invalid length when copying a later response (Rapid7, 2026-11-18), and Wiz demonstrated code execution on nginx serving ordinary static files (Wiz Research, 2026-11-18).
Rapid7 published a working proof of concept for CVE-2026-123007 against nginx 1.31.8; the exploit needs about 128 GB of HTTP/2 traffic and likely fails with concurrent clients (Rapid7, 2026-11-18; Rapid7 repository, 2026-11-18). Rapid7 says execution has the worker's permissions and root is not established; F5, as CERT.at relays it, frames the base effect as worker crashes, with code execution possible where ASLR is disabled or can be bypassed, which Wiz says attackers can do by reading memory first (translated from German) (Rapid7, 2026-11-18; CERT.at, 2026-11-18; Wiz Research, 2026-11-18). CERT-EU reports no exploitation in the wild, NCSC.ch rates exploitation unknown with a proof of concept available, and NCSC-NL expects large-scale exploitation once proof-of-concept code is public (translated from Dutch) (CERT-EU, 2026-11-18; NCSC.ch, 2026-11-18; NCSC-NL, 2026-11-18).
The fixes are in nginx 1.31.9 and 1.30.7 (nginx.org, 2026-11-18). CERT.at lists NGINX Plus 37.3.0.1 and 37.0.8.1 as fixing four of the five (CVE-2026-123007, CVE-2026-121810, CVE-2026-123633 and CVE-2026-113425); it also says 37.2.0.1 and 37.0.7.1 already carry the fix for CVE-2026-123633 but stay affected by CVE-2026-123007 and CVE-2026-121810, and NGINX Plus R33 to R36 have no update (translated from German) (CERT.at, 2026-11-18).
Triage: a large upload is a legitimate cause of an inbound-heavy connection and workers crash for unrelated reasons, so a program started by the worker is the discriminator, not the traffic shape alone (Xint, 2026-11-18).
Cited evidence
All five vulnerabilities can lead to unauthenticated code execution with the privileges of the NGINX worker process
no exploitation in the wild has been reported yet
Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data.
Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.
Until then, disabling HTTP/2 on affected listening ports blocks CVE-2026-123007 and CVE-2026-123633. It does not block the other three nginx vulnerabilities.
After installing the update, restart nginx or complete a supported live binary upgrade. A configuration reload alone does not replace the running executable.
Sources9
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.