Skip to main content
Intelligence Library
Threat IntelligenceLive

NGINX2Root: Critical nginx RCE Vulnerabilities (CVSS 9.2)

Flaws in nginx's HTTP/2 code give unauthenticated attackers code execution on one of the most widely used web servers, and a Linux kernel bug takes them to root. We are tracking developments as they happen.

NGINX2Root is a set of five nginx vulnerabilities disclosed on 18 November 2026. The most serious, CVE-2026-123007 (CVSS 9.2), is HTTP/2 memory corruption in nginx 1.9.5 to 1.31.8 that allows unauthenticated remote code execution; chained with a Linux SCTP kernel flaw it gives host root. Upgrade to nginx 1.30.7 or 1.31.9 now, or disable HTTP/2 until you can.

Published
Updating live, last update
Precursor Security

What you should do now

  1. Find every nginx, including ones inside appliances, load balancers, Kubernetes ingress and container images. Updating the host operating system does not patch a bundled copy.
  2. Upgrade to 1.30.7 or 1.31.9 (NGINX Plus 37.3.0.1 or 37.0.8.1), or your vendor's fixed package. Internet-facing servers with HTTP/2 enabled go first.
  3. Restart, do not just reload. nginx -s reload keeps the old binary running. Rebuild and redeploy container images; fixed official Docker images are out, but use nginx:1.31.9-alpine rather than nginx:alpine for now.
  4. Cannot upgrade today? Turn off HTTP/2 with http2 off; (nginx 1.25.1 and later) or remove http2 from the listen directive, then confirm from outside that h2 is no longer offered.
  5. Reduce the path to root: where SCTP is not needed, block the module with install sctp /bin/false in /etc/modprobe.d/ until a kernel fix ships.
  6. Hunt for signs of attempts: nginx worker crashes in the error log, nginx workers starting shells or new outbound connections, and long-lived HTTP/2 connections pushing very large volumes of data.

NGINX2Root live timeline

18 Nov 2026Pinned

What we know so far

NGINX2Root is the name Xint gave to five nginx vulnerabilities, each with a working exploit, plus a separate Linux kernel flaw that turns code execution in nginx into root on the host. The most serious, CVE-2026-123007, is memory corruption in nginx's HTTP/2 flow control that lets an unauthenticated attacker run commands as the nginx worker. It has been in every official release since HTTP/2 arrived in nginx 1.9.5 in 2015.

A second HTTP/2 flaw, CVE-2026-123633, is a use-after-free reachable when nginx proxies HTTP/2 traffic to a backend. Wiz and Rapid7 both score these flaws CVSS 4.0 9.2 (Critical). At least five teams found them independently: Xint, Wiz, Rapid7, Metnir and Ikotas Labs.

Fixes: nginx 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November, fix ten CVEs in total. NGINX Plus is fixed in 37.3.0.1 and 37.0.8.1. Exploit code: Rapid7 has published a proof of concept for CVE-2026-123007 on GitHub. Exploitation in the wild: none reported at the time of writing.

If you cannot upgrade today, turn HTTP/2 off on internet-facing listeners. That blocks the two HTTP/2 flaws, but not the other three CVEs, which affect the resolver, HTTP/3 and the mail proxy.

18 Nov 2026

Amazon Linux: nginx fixes pending on AL2, AL2023 and the 2027 preview

Amazon Linux has published its CVE page for CVE-2026-123007, rating it Important with a CVSS 3.1 score of 8.1. The nginx package is "Pending Fix" on Amazon Linux 2 (the nginx1 extra), Amazon Linux 2023 and the Amazon Linux 2027 preview, which also lists its nginx-awslc build.

That makes three major distributions, Red Hat, Ubuntu and Amazon Linux, with no nginx update yet, and Debian and SUSE still have no page. On EC2 instances running nginx from Amazon's packages, disable HTTP/2 on internet-facing listeners until the ALAS advisory ships, or put a load balancer that terminates HTTP/2 in front of them.

18 Nov 2026

Ubuntu: nginx fix needed on every supported release, none shipped yet

Ubuntu has published its CVE page for CVE-2026-123007, rating it High priority. The nginx package is marked "needed" on every listed release from Ubuntu 16.04 onwards, including 20.04, 22.04 and 24.04, which means a fix is required but has not been released. Only 14.04 is listed as not affected.

So apt upgrade will not fix this on Ubuntu today, just as dnf update will not on Red Hat. Debian, Amazon Linux and SUSE had not published pages at 17:00 GMT. If you run nginx from distribution packages, disable HTTP/2 on internet-facing listeners now and watch for a Ubuntu Security Notice.

18 Nov 2026

Fixed official nginx Docker images are out, but check the alpine tag

The official nginx images on Docker Hub were updated at about 16:53 GMT. nginx:latest and nginx:mainline now point to 1.31.9, and nginx:stable points to 1.30.7, with explicit 1.31.9, 1.30.7 and 1.31.9-alpine tags also published.

At 16:56 GMT the plain nginx:alpine tag still pointed to an image from 13 November, which is the vulnerable 1.31.8. If you build on Alpine, use nginx:1.31.9-alpine explicitly rather than nginx:alpine until it catches up.

Pull the new image, rebuild anything that uses it as a base, and redeploy. Restarting a running container keeps the old image, and images built on top of nginx need rebuilding by whoever maintains them.

18 Nov 2026

CERT Polska warns of NGINX2Root; the fixes are already out, not due tomorrow

Poland's national CERT, CERT Polska, warned at 16:40 GMT about the five critical nginx vulnerabilities known as NGINX2Root, highlighting CVE-2026-123007, and published an advisory with recommendations. It is the second national body to warn, after Japan's National Cybersecurity Office.

CERT Polska says the security fixes are scheduled for tomorrow, 19 November. That date comes from Xint's timeline, which is in Korea Standard Time. In the UK and Europe the fixed releases, nginx 1.30.7 and 1.31.9, are already available from nginx.org and have been since this afternoon. Do not wait until tomorrow to patch.

18 Nov 2026

Red Hat rates CVE-2026-123007 Critical; no RHEL fixes yet

Red Hat has published its CVE page for CVE-2026-123007 and rates it Critical, with a CVSS 3.1 score of 8.1. The nginx packages in Red Hat Enterprise Linux 10, RHEL 9 (including the nginx 1.24 and 1.26 module streams) and the RHEL 8 nginx 1.24 stream are all listed as "Under investigation", with no security updates yet.

That means a dnf update on RHEL will not fix this today. If you run nginx from Red Hat packages, disable HTTP/2 on internet-facing listeners now and watch Red Hat's page for errata. Debian, Ubuntu and Amazon Linux had still not published pages for the CVE at 16:46 GMT.

18 Nov 2026

Beware fake NGINX2Root exploits on GitHub

New GitHub repositories named after NGINX2Root and its CVE numbers are already appearing. After every headline vulnerability, some "proof of concept" code turns out to be malware aimed at the defenders and researchers who download it, or does nothing at all.

As of 16:41 GMT, the only genuine public exploit we know of is Rapid7's, published by Stephen Fewer. Xint and Wiz have said they are not releasing theirs, so anything claiming to be the Xint or Wiz exploit is not what it says.

To check whether you are exposed, use the version and configuration checks on this page rather than running someone else's exploit. If you must test one, read the code first, never run it on a workstation or production system, use a throwaway virtual machine with no credentials on it, and walk away from anything that ships compiled binaries, obfuscated code or asks you to install extra packages.

18 Nov 2026

Ikotas Labs calls it NGINX2Shell, found with OpenAI

Ikotas Labs, one of the five independent finders, announced the HTTP/2 flaw at 15:09 GMT under its own name, NGINX2Shell, describing it as a pre-authentication RCE in nginx 1.31.8, the current mainline release. It says the work was done with OpenAI from discovery through to disclosure, and that more is to come.

NGINX2Shell and NGINX2Root refer to the same nginx HTTP/2 flaw, CVE-2026-123007, which Ikotas says Rapid7, Wiz and Xint also found. NGINX2Root is Xint's wider name for all five nginx CVEs plus the Linux kernel chain. The fixes are the same either way: nginx 1.30.7 or 1.31.9.

18 Nov 2026

F5 rates all five NGINX2Root flaws critical, with no fix for older NGINX Plus

F5's out-of-band security notification for 18 November indexes all of today's advisories. Its individual advisories for the NGINX2Root flaws, CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425, score every one 9.2 (Critical) under CVSS 4.0 and 8.1 (High) under CVSS 3.1. That is well above the "medium" label nginx.org gives three of them, so treat all five as critical.

There is no fix for NGINX Plus R34 to R36 for any of the five; the mail proxy flaw also covers R33. F5 also lists the resolver flaw as affecting nginx 0.6.18 to 0.8.55 with no fix. Those releases are more than a decade old, so if you still have one, replace it.

The same notification covers separate fixes for BIG-IP, including iControl REST, iControl SOAP, APM and iRule vulnerabilities. They are not part of NGINX2Root, but if you run BIG-IP, check the notification today too.

18 Nov 2026

Wiz: its exploit defeats ASLR, despite F5’s caveat

F5's advisory says code execution needs ASLR to be disabled or bypassed. Wiz researcher Nir Ohfeld says Wiz achieved "reliable remote code execution (ASLR defeated)" on nginx serving only static files, with no backend or third-party modules. Do not rely on ASLR as a mitigation.

Ohfeld says Wiz found both HTTP/2 flaws with its own AI tool, Wiz Atlas, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to confirm their impact. With Xint and Ikotas Labs also crediting AI, at least three of the five finders used AI to find these bugs.

18 Nov 2026

Japan’s National Cybersecurity Office issues an nginx alert

Japan's National Cybersecurity Office (国家サイバー統括室) posted an alert at 16:04 GMT asking administrators to update nginx promptly, the first government warning we have seen. Japanese media are also calling the flaws "NGINX2Shell", which is the same issue under another name.

As of 16:36 GMT we have not seen guidance from the UK's NCSC, CISA or CERT-EU. CISA has not added any of the CVEs to its Known Exploited Vulnerabilities catalogue, which would signal confirmed attacks.

18 Nov 2026

nginx2root.com was registered 16 days before disclosure

Registry records show nginx2root.com was registered through Cloudflare on 2 November 2026 at 17:24 UTC. That was 17 days after Xint reported the flaws to F5 on 16 October, 6 days after its reports reached the nginx developers on 27 October, and 16 days before today's coordinated disclosure.

A named site with demos, FAQs and remediation steps prepared weeks in advance is now normal for headline vulnerabilities, as it was for PHP2Shell and Java4Shell. It also means the name existed in public DNS records before the fix did. Anyone watching new domain registrations could have spotted "nginx2root" on 2 November, although the domain gave away nothing about the bugs themselves.

For defenders the takeaway is the same as ever: the disclosure date was set well in advance, so vendors and distributions had time to prepare packages. If your supplier still has no fix for nginx today, ask them when it is coming, and disable HTTP/2 in the meantime.

18 Nov 2026

Official nginx Docker images still ship vulnerable 1.31.8

If you run nginx from the official Docker Hub image, pulling it again today still gets you a vulnerable build. At 16:22 GMT the nginx:latest and mainline tags were still 1.31.8, and no 1.31.9 or 1.30.7 tags had been published.

A fix is on its way. The image maintainers moved the build files to 1.31.9 and 1.30.7 at 16:00 GMT in docker-nginx, and the request to publish them, official-images pull request 22789, was opened at 16:19 and has not been merged yet.

Until the new tags appear, disable HTTP/2 in your container's nginx configuration. When they do, rebuild and redeploy: restarting a running container does not pull the new image. Check images that are built on top of nginx too.

18 Nov 2026

F5: no fix for NGINX Plus R34 to R36; BIG-IP and F5OS not affected

F5's advisory K000163926 lists NGINX Plus R34, R35 and R36 as vulnerable to CVE-2026-123007 with no fixed release. F5 says that where no fix exists for your branch, you should upgrade to one that has it: NGINX Plus 37.0.8.1 or 37.3.0.1. If you cannot move to 37.x straight away, turn off HTTP/2 on internet-facing listeners, which blocks both HTTP/2 flaws.

F5 scores the flaw 8.1 (High) under CVSS 3.1 and 9.2 (Critical) under CVSS 4.0, calls it a data plane issue with no control plane exposure, and says code execution needs ASLR to be disabled or bypassed. Rapid7, Wiz and Xint all report working exploits, so do not treat that as protection. F5's advisory lists no mitigation of its own.

BIG-IP (all modules), BIG-IQ, F5OS, BIG-IP CNF, BIG-IP Next for Kubernetes and F5 AI Gateway are not vulnerable. F5 is still checking F5 Distributed Cloud and NGINX One Console. F5 credits Rapid7, Wiz, Xint and Ikotas Labs, which it says used GPT-6 Astra.

18 Nov 2026

Rapid7 publishes a working exploit for CVE-2026-123007, with real-world limits

Stephen Fewer of Rapid7, one of the independent finders, has released a proof-of-concept exploit alongside Rapid7's write-up. It gets unauthenticated code execution against a linux/amd64 Docker image running nginx 1.31.8 with HTTP/2 and TLS on.

It is not trivial to use at scale. Rapid7 says the attack needs roughly 128 GB of HTTP/2 traffic over one connection: about two minutes on a 10 Gbit/s link, seventeen minutes at 1 Gbit/s, and probably not achievable below about 300 Mbit/s with nginx's default one-hour connection limit. It also relies on a specific glibc memory copy routine chosen on CPUs with AVX-512, and HTTP/2 connections that pass through a proxy will probably not work.

Those limits buy time; they are not a fix. Public code is the point at which scanning and copycat exploit attempts usually start, so treat internet-facing nginx with HTTP/2 enabled as urgent.

18 Nov 2026

Xint launches nginx2root.com: five nginx CVEs plus a Linux kernel bug to host root

Xint (part of Theori) announced the disclosure and published nginx2root.com and a technical blog. It says each of the five nginx flaws has its own working exploit:

  • CVE-2026-123007: HTTP/2 flow control memory corruption. Needs HTTP/2 enabled.
  • CVE-2026-123633: HTTP/2 use-after-free when requests are forwarded to a backend.
  • CVE-2026-123634: DNS resolver use-after-free, reached with resolver, a request-dependent proxy_pass and mirror.
  • CVE-2026-121810: HTTP/3 (QUIC) use-after-free when requests are forwarded to a backend.
  • CVE-2026-113425: mail proxy use-after-free in the auth_http path.

The sixth bug is in the Linux kernel's SCTP code (since Linux 4.15) and has no patch yet. Xint used it to go from the nginx worker account to root, and says the chain also escaped a Docker container running nginx. Until a kernel fix ships, Xint suggests stopping the SCTP module from loading with install sctp /bin/false in a file under /etc/modprobe.d/. That does not unload a module already in use or disable SCTP built into the kernel.

On reach, Xint's Shodan snapshot of 10 November found 11.8 million of 11.94 million version-identifiable nginx hosts (98.9%) running a release in the CVE-2026-123007 range. That measures version spread, not confirmed exploitable servers: many will not expose HTTP/2, and distribution packages may carry the fix under an older version number.

18 Nov 2026

Wiz: two critical nginx HTTP/2 RCEs, found by five teams independently

Wiz Research posted on X that it, Xint, Metnir, Rapid7 and Ikotas Labs independently found CVE-2026-123633 and CVE-2026-123007, and published a full advisory. Wiz rates both CVSS 4.0 9.2 and says it got code execution against nginx serving plain static files, with no backend application or third-party module.

Wiz is not releasing its exploits and says reliable attacks take real work: leaking memory addresses, shaping the heap and adjusting for each build. It expects the first wide attacks to hit packaged products that ship identical nginx builds, such as appliances and container images.

For detection, Wiz suggests watching for unexpected nginx worker crashes, commands started by nginx, and long-lived HTTP/2 connections sending large amounts of data, since CVE-2026-123007 needs many WINDOW_UPDATE frames. It notes that a CDN or WAF that terminates HTTP/2 in front of nginx may partly reduce the risk.

Release18 Nov 2026

nginx 1.30.7 and 1.31.9 released, fixing ten CVEs at once

The nginx project released 1.30.7 (stable) and 1.31.9 (mainline) with fixes for ten vulnerabilities: the five NGINX2Root flaws plus five more. The extra five are an infinite loop while reading a request body over TLS 1.3 (CVE-2026-118899), a NULL pointer dereference with PROXY protocol version 2 (CVE-2026-120993, mainline only), a buffer overflow with alias and try_files (CVE-2026-125283), an SNI bypass in stream module client certificate checks (CVE-2026-120967) and weak validation in the stream ssl_preread module (CVE-2026-123640).

nginx's own advisories label CVE-2026-123007 and CVE-2026-113425 "major" and CVE-2026-123633, CVE-2026-123634 and CVE-2026-121810 "medium", below the CVSS 9.2 that Wiz and Rapid7 give the HTTP/2 flaws. Do not let the "medium" label slow you down: Wiz and Xint both report working code execution exploits for CVE-2026-123633.

For NGINX Plus, F5 advisory K000163926 covers the fixes: 37.3.0.1 and 37.0.8.1 for CVE-2026-123007, and 37.2.0.1 and 37.0.7.1 for CVE-2026-123633. This is nginx's second security release in five weeks, after 1.30.6 and 1.31.7 fixed five other CVEs on 14 October.

Confirmed17 Nov 2026

F5 confirms Wiz’s second report is CVE-2026-123007, already in the planned release

One day after Wiz reported the HTTP/2 flow control bug, F5 told it the issue matched CVE-2026-123007 and was already fixed in the release planned for 18 November, according to Wiz's timeline. By this point at least four teams had reported the same bug.

CVE16 Nov 2026

CVE-2026-123007 assigned and 18 November disclosure date set; Wiz reports the same bug

F5 validated Rapid7's report, assigned CVE-2026-123007 and set coordinated disclosure for 18 November, per Rapid7's timeline. The same day, Wiz reported the flow control bug to F5 as a separate issue from the use-after-free it had reported in October.

Outreach11 Nov 2026

Rapid7 contacts F5 about an HTTP/2 flaw and shares details the next day

Stephen Fewer of Rapid7 made initial contact with F5 on 11 November. F5 confirmed on 12 November and Rapid7 sent the technical details that day. Rapid7 went on to build the proof-of-concept exploit it released on disclosure day.

Patch10 Nov 2026

Patches go out for review; Xint takes its exposure snapshot

F5 sent Wiz a patch for the HTTP/2 use-after-free (CVE-2026-123633) to review, and the nginx team asked Xint to validate its fixes, which Xint completed the same day. Xint also ran the Shodan snapshot behind its exposure figure: 11.8 million of 11.94 million version-identifiable nginx hosts in the affected range for CVE-2026-123007.

Handover27 Oct 2026

Xint’s reports reach the nginx development team

Eleven days after Xint first reported, its findings were passed from F5's HackerOne programme to the nginx developers, according to the Xint blog. HackerOne had completed validation on 20 October.

Wiz21 Oct 2026

Wiz reports the HTTP/2 use-after-free and learns it is a duplicate

Wiz Research reported the bug that became CVE-2026-123633 to F5, which replied that another team had already reported it. Wiz says the flaw happens when an HTTP/2 connection is wrongly left on nginx's list of reusable connections while a request is still active, so nginx can free it mid-request when connection slots run low.

Reported16 Oct 2026

Xint reports the nginx flaws to F5 through HackerOne

Five days after finding them, Xint submitted its reports to F5, nginx's owner, through HackerOne. Xint's dates are in Korea Standard Time, nine hours ahead of the UK. It counts 39 days from discovery to fix.

Found11 Oct 2026

Xint finds the first bug with an AI-assisted scan and a human researcher

While testing a new capability ahead of Wiz's ZeroDay Cloud competition, a Xint researcher pointed the tool at about 50,000 lines of nginx. Within 90 minutes it flagged high-severity issues with reproduction steps that became a working exploit in under ten minutes, Xint says.

The researcher personally found CVE-2026-123007, the HTTP/2 flaw that affects a default nginx setup with HTTP/2 on. Xint then built what it learned into its general tooling, which found the other four nginx bugs with no human guidance. The flawed code had been in nginx since HTTP/2 support arrived in version 1.9.5 in 2015.

NGINX2Root key facts

Main CVE
CVE-2026-123007, HTTP/2 flow control memory corruption. CVSS 4.0 9.2 (Critical); F5 rates all five NGINX2Root CVEs 9.2.
Affected
nginx 1.9.5 to 1.31.8 with HTTP/2 enabled. NGINX Plus 37.x before 37.3.0.1 and 37.0.8.1, and R34 to R36, which get no fix.
Fixed in
nginx 1.30.7 (stable) and 1.31.9 (mainline), released 18 November 2026.
Impact
Unauthenticated remote code execution as the nginx worker; root on the host when chained with an unpatched Linux SCTP kernel flaw.
Exploit status
Public proof of concept from Rapid7. No exploitation in the wild reported at the time of writing.
Workaround
Disable HTTP/2 on every internet-facing listener until you can upgrade.

The five nginx CVEs at a glance

CVEFlawExposed whenHTTP/2 off helps?
CVE-2026-123007HTTP/2 flow control memory corruptionHTTP/2 enabled. Versions 1.9.5 to 1.31.8Yes
CVE-2026-123633HTTP/2 use-after-freeHTTP/2 with requests passed to a backend (proxy_pass, fastcgi_pass, grpc_pass). Versions 1.19.7 to 1.31.8Yes
CVE-2026-123634Resolver use-after-freeresolver, proxy_pass, mirror and mirror_request_body off together. Versions 0.6.18 to 1.31.8No
CVE-2026-121810HTTP/3 use-after-freeHTTP/3 (QUIC) with requests passed to a backend. Versions 1.25.0 to 1.31.8No
CVE-2026-113425Mail proxy use-after-freeMail proxy with proxy on and auth_http. Versions 0.5.33 to 1.31.8No

All five are fixed in nginx 1.30.7 and 1.31.9. Configurations from Xint's disclosure, version ranges from the nginx security advisories. Distribution packages may carry the fix under an older version number.

Why this one is different: pre-auth RCE in nginx is rare

nginx serves roughly a third of websites whose web server can be identified, and it has been fuzzed and audited for two decades. Xint says the best known previous pre-authentication RCE in nginx dates from 2013. This time five teams, several using AI-assisted tooling, found the same HTTP/2 bugs within weeks of each other.

When that many people find a bug independently, assume others have too. With exploit code now public, the gap between disclosure and attack attempts will be short.

NGINX2Root frequently asked questions

What is NGINX2Root?

NGINX2Root is the name Xint (Theori) gave to five nginx vulnerabilities disclosed on 18 November 2026, CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425, plus a separate Linux kernel SCTP flaw. Each nginx flaw has a working exploit for code execution as the nginx worker, and chaining one with the kernel flaw gave root on the host, including from inside a Docker container.

Which nginx versions are affected by CVE-2026-123007?

Official nginx releases from 1.9.5 to 1.31.8 are affected, which covers every release since HTTP/2 support was added in 2015. A server is only exposed if nginx is built with HTTP/2 and a listener accepts HTTP/2 connections. NGINX Plus 37.x releases before 37.3.0.1 and 37.0.8.1 are also affected, as are NGINX Plus R34 to R36, which F5 will not fix. BIG-IP, BIG-IQ and F5OS are not affected. Distribution packages may have backported the fix without changing the version number, so check your vendor advisory.

Which versions fix NGINX2Root?

nginx 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026, fix all five NGINX2Root CVEs and five other nginx CVEs. For NGINX Plus, upgrade to 37.3.0.1 or 37.0.8.1; there is no fix for R34 to R36, so move those to 37.x. Restart nginx after upgrading: a configuration reload does not load the new binary.

Does disabling HTTP/2 protect against NGINX2Root?

Partly. Disabling HTTP/2 blocks the two most serious flaws, CVE-2026-123007 and CVE-2026-123633. It does not address CVE-2026-123634 (resolver with mirror), CVE-2026-121810 (HTTP/3 proxying) or CVE-2026-113425 (mail proxy auth_http). On nginx 1.25.1 and later set http2 off; in each server block; on older versions remove http2 from the listen directive. Then reload and confirm from outside that the server no longer negotiates h2.

Is NGINX2Root being exploited?

At the time of writing no exploitation in the wild has been reported. However, Rapid7 has published a proof-of-concept exploit for CVE-2026-123007 on GitHub, and Xint and Wiz both have working exploits they are not releasing. Public exploit code usually brings scanning and attack attempts within days. Beware fake exploits on GitHub: some carry malware, so only test code you have read, in an isolated virtual machine.

How do I check if my nginx server is vulnerable?

Check the version with nginx -v, then whether HTTP/2 is active: look for http2 in your listen directives or an http2 on; directive, and test from outside with openssl s_client -alpn h2 against the host. Also check for resolver with mirror, HTTP/3 proxying and the mail proxy with auth_http, which are affected by the other three CVEs. For distribution packages, appliances and container images, rely on the vendor advisory rather than the version string.

Does a CDN or load balancer in front of nginx protect me?

Only if it terminates HTTP/2, forwards requests to nginx over HTTP/1.1, and direct access to nginx is blocked. Then the HTTP/2 flaws cannot be reached through it, and Rapid7 says its exploit probably fails over proxied HTTP/2. If the front end uses TLS passthrough or speaks HTTP/2 to nginx, nginx is still exposed. nginx is also often the load balancer itself. Patch regardless.

Is NGINX2Root the same as CVE-2026-123007?

CVE-2026-123007 is the headline NGINX2Root flaw, but NGINX2Root covers five nginx CVEs: CVE-2026-123007 (HTTP/2 flow control), CVE-2026-123633 (HTTP/2 use-after-free), CVE-2026-123634 (resolver use-after-free), CVE-2026-121810 (HTTP/3 use-after-free) and CVE-2026-113425 (mail proxy use-after-free), plus a Linux kernel SCTP flaw without a CVE at disclosure. Wiz and Rapid7 refer to the HTTP/2 flaws by CVE number rather than the NGINX2Root name.

What can an attacker do with NGINX2Root?

Each nginx flaw lets an unauthenticated attacker run commands as the nginx worker process. From there they can read application data, credentials and secrets the worker can reach, and talk to internal services. Chained with the Linux SCTP kernel flaw, Xint reached root on the host, including escaping a Docker container.

Am I safe if nginx is only on my internal network?

No. Restricting access limits who can reach nginx but does not remove the flaw. An attacker who already has a foothold inside your network could use it to move laterally. Include internal nginx servers, ingress controllers and reverse proxies in your patching.

Will disabling HTTP/2 break my application?

Most browsers and web clients fall back to HTTP/1.1, possibly with some loss of performance. gRPC needs HTTP/2, so gRPC services behind nginx will stop working if you turn HTTP/2 off. Test before changing production, and patch instead where HTTP/2 is required.

Can a WAF or rate limiting replace patching?

No. Web application firewall rules inspect URLs and request bodies, but the HTTP/2 flaws are triggered by low-level control frames such as WINDOW_UPDATE and RST_STREAM. Use a WAF or connection limits only alongside patching or disabling the affected features.

How do I tell if my nginx server was attacked?

Ordinary access logs do not record the HTTP/2 control frames used in these attacks, so a clean access log proves nothing. Look at the nginx error log for repeated worker crashes, process execution records for nginx workers starting shells or other programs, and network data for long-lived HTTP/2 connections moving unusually large amounts of data. If you confirm compromise, isolate the host, rotate any secrets the worker could read, and rebuild from a trusted image.

Who found NGINX2Root?

Xint, the AI security platform from Theori, found and named NGINX2Root: researchers Soomin Shin, Joohyun Park, Tim Becker and Yves Bieri. The two HTTP/2 flaws were also found independently by Wiz Research, Rapid7 (Stephen Fewer), Metnir and Ikotas Labs.

Does patching nginx close the whole NGINX2Root chain?

It closes the remote entry point. The Linux kernel SCTP flaw that escalates from the nginx worker to root is separate and had no kernel patch at disclosure. Until one ships, Xint suggests blocking the SCTP module from loading with install sctp /bin/false in /etc/modprobe.d/, where SCTP is not built into the kernel and not already loaded.

Need help responding to NGINX2Root?

Precursor's CREST-accredited SOC monitors for active exploitation 24/7. If you need help finding exposed nginx servers, prioritising patching or investigating a suspicious crash, we can help.