HIGHLIGHT OF THE DAY · CYBERSECURITY
NGINX fixes and public exploit raise urgency; disabling HTTP/2 is only partial protection
Fixed NGINX releases and a public code-execution exploit make patching urgent. A government SOC reports attacks, but public corroboration remains limited, and neither universal root access nor widespread successful exploitation is established.
· 5 min read · 14 sources
Briefing24 · AI-assisted research and analysis · Methodology
Released fixes and public exploit code change the response
NGINX administrators now have both released fixes and public exploitation material to account for. The official security advisory identifies stable 1.30.7 and mainline 1.31.9 as fixed for five vulnerabilities grouped under NGINX2Root. Wiz dates the coordinated disclosure and security release to November 18, following reports it submitted on October 21 and November 16. This is a patch-and-verification problem, not a warning about fixes still being developed. [1][2]
Rapid7 published a proof of concept demonstrating unauthenticated remote code execution against a Linux/amd64 Docker image running NGINX 1.31.8 with HTTP/2 and TLS enabled. Separately, Wiz demonstrated exploitation through ordinary static-file serving, without requiring a vulnerable backend application or third-party module. Because an NGINX deployment can serve several websites or APIs, compromise can expose multiple services to data theft, content changes or disruption. [2][3]
Five separate flaws require a configuration inventory
The five flaws are independent vulnerability paths, not stages that must all be chained. CVE-2026-123007 affects HTTP/2 flow control. CVE-2026-123633 involves HTTP/2 reverse proxying under connection-slot pressure. Their shared protocol matters for temporary containment, but administrators need to identify the features actually enabled rather than treating every NGINX installation as equally exposed. [1][6]
The remaining paths involve different configurations: HTTP/3/QUIC reverse proxying with additional connection conditions for CVE-2026-121810; dynamic DNS resolution of variable upstream names with overlapping SSI or mirror subrequests for CVE-2026-123634; and mail-proxy authentication lookup functionality for CVE-2026-113425. Disabling HTTP/2 does not address those configurations. [1][6][9]
SecurityWeek's November 19 report attributes to Censys an estimate of approximately nine million services advertising affected versions with HTTP/2 enabled. That is not a count of confirmed exploitable machines, organizations or victims. Censys warns that distribution packages may carry backported fixes without changing their upstream version number, limiting what an advertised version alone establishes. [5][6]
Independent testing confirms bugs, not every takeover claim
Rapid7's demonstrated exploit requires approximately 128 GB of HTTP/2 traffic and depends on a particular x86-64 glibc memory-copy implementation selected through CPU features. Bandwidth, connection lifetime and intermediaries therefore affect feasibility. Those are constraints on this implementation, not proof that other approaches cannot work. Wiz separately reports successful exploitation with an ASLR bypass, so enabled address-space randomization is not sufficient grounds to declare protection. [2][3]
Censys independently reproduced erroneous HTTP/2 flow-control behavior with a 5.69 MB test, but that test neither crashed the worker nor achieved code execution. It also reproduced three use-after-free conditions without code execution and did not reproduce the HTTP/3 issue. This corroborates underlying defects, not a few-megabyte replacement for Rapid7's full exploit. SecurityWeek's reporting of researchers' findings is not another independent exploit validation. [5][8]
The name also overstates the outcome if read literally. Initial NGINX exploitation provides worker-process privileges. Xint reports reaching host root and escaping a Docker container by chaining an NGINX exploit with a separate Linux SCTP kernel vulnerability. Reachability depends on the kernel, modules and container restrictions. Censys explicitly has not verified that kernel flaw or chain, so universal host-root compromise is not established. [8][9]
November 19 attack reports remain inconsistent
Western Australia's government SOC says it has been informed of exploitation of one or more of the two HTTP/2 vulnerabilities. Its November 19 advisory supplies no victim details or supporting telemetry and reports no incidents on Western Australian government networks. This is an attributable government warning, but the public information does not establish attack scale. [4]
F5 told The Register on November 18 that it had found no evidence of active exploitation, and CERT-EU that day said in-the-wild exploitation had not been reported. Those statements may predate newer information. However, watchTowr still reported no known in-the-wild exploitation as of November 19. The defensible synthesis is that an attack warning exists, while corroborating incident details remain unavailable in these sources. [4][10][11][12]
Verify the correct package and replace the running binary
For upstream open-source deployments, use the fixed stable or mainline branch rather than a simple numerical comparison: affected mainline 1.31.8 sorts above fixed stable 1.30.7. Distribution users should check their vendor's advisory. AlmaLinux says supported streams received backports, but retired streams, including its default AlmaLinux 8 nginx:1.14 stream, were excluded. An old-looking version can be patched; an unsupported stream can remain exposed. [1][6][13]
NGINX Plus requires separate checks. Its release notes identify PLS.37.0.8.1 LTS and PLS.37.3.0.1 CR for November 18, while recording CVE-2026-123633 as fixed in earlier October 14 releases. Administrators should not assume identical release histories across products. After installing the appropriate fixed package, restart the service: Censys warns that a configuration reload alone does not replace the running binary. [7][8]
Containment and managed-service updates need verification
Disabling HTTP/2 temporarily addresses the two HTTP/2 paths, not the HTTP/3, resolver or mail-proxy vulnerabilities. It can also disrupt services that require HTTP/2, including native gRPC. The operational inference is that containment must follow a configuration inventory and service-impact check, rather than a blanket assumption that one protocol change substitutes for patching. [6][9]
Microsoft began updating Azure App Service Linux PHP and WordPress images on November 18, expecting completion by the end of November 19 Pacific time, conditional on validation. That schedule is not confirmation of completion. Microsoft says its front-end load balancers block this HTTP/2 RCE path to application workers, but custom-container owners must rebuild and redeploy their own images. [14]
Preserve evidence and watch for corroborated incidents
Investigations should correlate worker crashes and HTTP/2 errors with unexpected child processes or outbound connections from workers. Crashes alone do not prove compromise. Censys also cautions that its experimental network signatures are not validated general-purpose exploit detectors, so a detection result or its absence should not be treated as a definitive compromise assessment. [8]
The next evidence to watch is corroborating detail behind the government exploitation warning, confirmation of managed-service rollout completion, and further independent testing of the claimed root-access chain. Our assessment is that these uncertainties should shape incident claims, not delay remediation: official fixes, demonstrated code execution and independently reproduced vulnerable behavior already establish a concrete defensive priority. [1][3][4][8][14]
Sources & further reading
- nginx security advisories ↗nginx.org
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 | Wiz Blog ↗www.wiz.io
- Rapid7 discloses a critical vulnerability affecting NGINX HTTP/2 that can lead to remote code execution ↗www.rapid7.com
- NGINX2Root Active Exploitation - 20261119001 - WA Cyber Security Unit (DGOV Technical) ↗soc.cyber.wa.gov.au
- F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public - SecurityWeek ↗www.securityweek.com
- Nov 18 Advisory: NGINX Memory Corruption Vulnerabilities (nginx2root) - Censys ↗censys.com
- Releases | NGINX Documentation ↗docs.nginx.com
- nginx2root: A simple test for the HTTP/2 flaw and three use-after-free reproductions - Censys ↗censys.com
- NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching - Xint Blog | Insights from Offensive Security Researchers ↗xint.io
- AI found more critical bugs in another widely used technology running 225M websites ↗www.theregister.com
- CERT-EU - Critical vulnerabilities in Nginx ↗cert.europa.eu
- NGINX2root (CVE-2026-123633) FAQ: NGINX "NGINX2root" RCE ↗watchtowr.com
- NGINX2Root: Patched nginx packages released | AlmaLinux OS ↗almalinux.org
Researched, written and checked with GPT-6 Astra. Publication is automatic after source, structure and model review checks. These checks can miss errors and do not constitute human verification.
Report a correction · Browse highlights · Read the daily briefing