CyberSIXT reportingUpdated
nginx2root (NGINX2Shell): CVE-2026-123007 RCE exploit published
Part of the CVE-2026-123007 story · since 18 Nov
- Wed 18 Nov, 15:25 UTC. cybersixt, first report. nginx2root (NGINX2Shell): CVE-2026-123007 RCE exploit published. This article, 1st of 2.
- Wed 18 Nov, 17:00 UTC. Infosecurity, its first report on the story. Five NGINX flaws could let attackers take control of websites.
Updated 18 November, 16:43 UTC. Rapid7 has published exploit code for CVE-2026-123007 and says it needs about 128 GB of HTTP/2 traffic.
Five newly disclosed nginx vulnerabilities each lead to remote code execution by an unauthenticated attacker, according to Xint, whose researchers found them, and the most widely exposed one, CVE-2026-123007, needs nothing more than HTTP/2 to be enabled. Xint calls the set nginx2root; Ikotas Labs, one of the teams F5 credits with finding CVE-2026-123007, calls its finding NGINX2Shell and says it worked with OpenAI. F5, which maintains nginx, published advisories on 18 November in an out-of-band security notification, rates all five 8.1 under CVSS 3.1 and 9.2, critical, under CVSS 4.0, and says code execution depends on ASLR being disabled or bypassed.
nginx 1.31.9 (mainline) and 1.30.7 (stable), the open-source releases F5 lists as fixed, were on nginx.org and tagged on GitHub on 18 November. NGINX Plus 37.3.0.1 and 37.0.8.1 fix CVE-2026-123007. The changelog shipped with 1.31.9 lists ten security fixes: the five flaws and five others, a buffer overflow with try_files and alias (CVE-2026-125283), an endless loop while reading a request body over SSL (CVE-2026-118899) and three stream module issues. It describes CVE-2026-123007 more cautiously than the researchers, as a flow control window overflow that "might allow an attacker to cause a segmentation fault in a worker process, or might have potential other impact". nginx's own security advisories page rates CVE-2026-123007 and the mail proxy flaw "major" and the other three "medium". Red Hat, Ubuntu, Debian, SUSE and Alpine had not yet published records for CVE-2026-123007.
Which servers are exposed
The five flaws are separate attack paths and need different configurations, according to F5's advisories and Xint's write-up:
- CVE-2026-123007: HTTP/2 enabled; every release from 1.9.5 (2015) to 1.31.8. Wiz Research ran code on a server serving only static files, with no backend or third-party module.
- CVE-2026-123633: a use-after-free; HTTP/2 with requests proxied to a backend, when the worker is running low on connections (advisory); since 1.19.7.
- CVE-2026-123634: a
proxy_passtarget built from variables and looked up by nginx's resolver, plus amirroror SSI subrequest to the same name. - CVE-2026-121810: HTTP/3 with requests proxied to a backend; since 1.25.0.
- CVE-2026-113425: nginx used as a mail proxy with
auth_http.
How CVE-2026-123007 works
nginx subtracts queued response data from a connection's flow-control counter, and when a stream is cancelled it adds the unsent amount back without checking the HTTP/2 maximum. If the client has already raised the window, the counter ends up above the limit, a later unsigned bounds check wraps around, and a negative length reaches the TLS send path, where it becomes an out-of-bounds memory copy, Wiz and Xint explain.
Xint says it used this to leak memory addresses and overwrite a connection cleanup function pointer, running commands as the nginx worker. Both teams report bypassing ASLR; Wiz confirmed code execution on official 1.31.7 and 1.31.8 builds over TLS on 64-bit systems.
Public exploit code
Rapid7 published proof-of-concept code for CVE-2026-123007 on 18 November with its analysis. It runs a command without authentication on the official linux/amd64 Docker image of nginx 1.31.8 with HTTP/2 and TLS enabled, as the nginx worker; Rapid7 says execution as root "has not been established".
The attack has to send about 128 GB of HTTP/2 data, which it says takes two minutes at 10 Gbit/s and seventeen minutes at 1 Gbit/s, and fails below roughly 300 Mbit/s because nginx closes a connection after one hour by default. It is unlikely to work through a proxy, and it depends on a glibc memory-copy routine chosen on x86-64 processors with AVX-512 (avx512f and avx512vl). "Alternative RCE exploitation strategies may be viable, but none are currently known," Rapid7 writes.
The Linux kernel flaw
Xint also found an unpatched use-after-free in the Linux kernel's SCTP code, present since Linux 4.15 in 2018, and chained it with CVE-2026-123007 to get root on the host, including from nginx running in a Docker container. It is withholding the details until a kernel fix exists and has not published a CVE for it. Hosts that do not use SCTP can stop the module from loading with install sctp /bin/false under /etc/modprobe.d/, Xint says.
Who found them
F5 credits Rapid7's Stephen Fewer, Tomer Schwartz of Wiz, Xint and Ikotas Labs, which F5 says used OpenAI's GPT-6 Astra, for CVE-2026-123007, and Albert Ebb of Metnir and Nir Ohfeld of Wiz for CVE-2026-123633. Xint reported its findings on 16 October, Wiz reported CVE-2026-123633 on 21 October and Rapid7 disclosed CVE-2026-123007 to F5 on 12 November.
What to do
Install nginx 1.31.9 or 1.30.7, NGINX Plus 37.3.0.1 or 37.0.8.1, or your distribution's package once it is published, then restart nginx: Xint notes that nginx -s reload does not load a new binary. Where an update has to wait, set http2 off; in each affected server block on nginx 1.25.1 and later, or remove http2 from the listen directive on older versions, and check from outside that the server no longer offers h2. That blocks only CVE-2026-123007 and CVE-2026-123633; the other three need the configuration changes in Xint's write-up. A patched distribution package can still report an old version in nginx -v, Xint warns; the full package version is what to compare with the distribution's advisory.
What is not known
None of the researchers or F5 report attacks in the wild. Wiz says it will not release its exploits for now. F5 is still assessing whether its Distributed Cloud services and NGINX One Console are affected.
How the story developed
2 articles from 2 outlets since 18 Nov. Still developing; the latest report was 2 hours ago. This was the first report.
- Wed 18 Nov, 15:25 UTC. cybersixt, first report. nginx2root (NGINX2Shell): CVE-2026-123007 RCE exploit published. This article, 1st of 2.
- Wed 18 Nov, 17:00 UTC. Infosecurity, its first report on the story. Five NGINX flaws could let attackers take control of websites.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 2 articles as a listHide the list
- Wed 18 NovDay 02
- nginx2root (NGINX2Shell): CVE-2026-123007 RCE exploit published15:25 · cybersixt · First report · This article, 1st of 2
- Five NGINX flaws could let attackers take control of websites17:00 · Infosecurity
Sources
- F5: Out-of-band Security NotificationPrimary sourcemy.f5.com
- F5: NGINX ngx_http_v2_module vulnerability CVE-2026-123007Primary sourcemy.f5.com
- F5: NGINX ngx_http_v2_module vulnerability CVE-2026-123633Primary sourcemy.f5.com
- Xint: nginx2root write-upPrimary sourcexint.io
- Wiz Research: NGINX HTTP/2 remote code execution vulnerabilitiesPrimary sourcewiz.io
- Ikotas Labs on NGINX2ShellPrimary sourcex.com
- nginx security advisoriesnginx.org
- nginx on GitHub: release-1.31.9Primary sourcegithub.com
More reporting
- Drupal vulnerability CVE-2026-132165 can lead to takeover18 Nov
- Visa data breach claim: supplier blamed as n0n names 5918 Nov
- LUKSO email recovery flaw lets attacker drain 300 profiles18 Nov
- Valcour security incident takes Vermont police system offline18 Nov
- Airbyte Cloud taken offline after cyberattack, syncs halted18 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS