--- title: "NGINX HTTP/2 RCE CVE-2026-123007: Patch Now, What to Do" url: https://playciso.com/blog/nginx-http2-rce-cve-2026-123007 updated: 2026-11-19 section: Blog publisher: PlayCISO --- # NGINX HTTP/2 RCE CVE-2026-123007: Patch Now, What to Do > NGINX HTTP/2 flaws CVE-2026-123007 and CVE-2026-123633 can let attackers run code. Fixed in 1.30.7 and 1.31.9. Check http2, patch, stopgap. Source: https://playciso.com/blog/nginx-http2-rce-cve-2026-123007 · Published: 2026-11-19 · Publisher: PlayCISO (https://playciso.com) Primary source: https://nginx.org/en/security_advisories.html --- **nginx.org and F5 fixed two HTTP/2 flaws in NGINX on 18 November 2026 that can let an unauthenticated attacker crash the server or, in some conditions, run code on it.** CVE-2026-123007 (a flow-control window overflow) and CVE-2026-123633 (a use-after-free) are both in the HTTP/2 module and are fixed in **nginx 1.30.7** (stable) and **1.31.9** (mainline). F5 scores each CVSS 4.0 **9.2**. Both need HTTP/2 to be in use. No exploitation in the wild was reported by 19 November, but a public proof of concept exists for CVE-2026-123007, so treat this as a patch-this-week item for every internet-facing NGINX that speaks HTTP/2. **Update, 19 November 2026:** Xint says it chained CVE-2026-123007 with a separate, unpatched Linux kernel flaw in the SCTP subsystem to escape a Docker container running NGINX and get root on the host. That is a researcher demonstration, not a reported attack. Wiz demonstrated code execution against a server hosting ordinary static files over HTTP/2 with TLS, and against CVE-2026-123633, without releasing those exploits. Version-based exposure counts overstate the risk. See [Container escape to host root (Xint)](#container-escape) and [How many servers are exposed](#exposure). **Who this is for:** CISOs, platform and SRE leads, and anyone who runs NGINX or NGINX Plus as a web server, reverse proxy or load balancer, or buys a product that ships it. *Based on nginx.org's advisories and changelog, the CVE records F5 published, CISA's KEV catalog, Ubuntu and Debian security data, the Wiz, Rapid7 and Xint write-ups and BleepingComputer's report, all read on 19 November 2026. F5's own K-articles did not load for us, so F5 facts are taken from the CVE records F5 authored. PlayCISO is not affiliated with F5. We publish no exploit details.* Confirmed vs not yet known **Confirmed by nginx.org and F5:** two HTTP/2 module flaws, fixed in 1.30.7 and 1.31.9 on 18 November 2026. F5 says each can crash an NGINX worker and that "attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR". Both are "data plane" issues with "no control plane exposure", per F5. F5's records list no workaround. **Conditions:** CVE-2026-123007 affects "configurations that use HTTP/2". CVE-2026-123633 needs HTTP/2 for client connections, proxying to a backend, and a worker "running low on worker_connections". **Exploitation:** not in CISA KEV (catalog 2026.11.18); CISA's SSVC entry says Exploitation: none (18 November). Rapid7 published a proof of concept for CVE-2026-123007; Wiz says it has exploits for both and is not releasing them. **Claimed by researchers, not an incident:** Xint says it chained CVE-2026-123007 with an unpatched Linux kernel SCTP flaw to go from an NGINX Docker container to root on the host. The kernel flaw has no CVE ID or fix yet. **Not stated by any source we could read:** the kernel flaw's CVE ID, the kernel versions that will fix it, and the Docker settings (seccomp, capabilities, privileged or not) in Xint's test; whether NGINX Ingress Controller, NGINX Gateway Fabric or other F5 products are affected. Check F5's [K000163926](https://my.f5.com/manage/s/article/K000163926) and [K000163928](https://my.f5.com/manage/s/article/K000163928) directly. ## The two HTTP/2 flaws | | CVE-2026-123007 | CVE-2026-123633 | | --- | --- | --- | | What | HTTP/2 flow-control window overflow leading to a heap buffer overflow (CWE-191, CWE-787) | Use-after-free in HTTP/2 connection handling (CWE-416) | | Needs | HTTP/2 in use. Wiz says default HTTP/2 configs are exposed, including servers that only serve static files | HTTP/2 for client connections, proxying to a backend, worker low on worker_connections | | nginx.org severity | Major | Medium | | F5 CVSS | 3.1: 8.1 (AV:N/AC:H/PR:N/UI:N) · 4.0: 9.2 | 3.1: 8.1 (AV:N/AC:H/PR:N/UI:N) · 4.0: 9.2 | | Open Source vulnerable | 1.9.5 to 1.31.8 | 1.19.7 to 1.31.8 | | Open Source fixed | 1.30.7, 1.31.9 | 1.30.7, 1.31.9 | | NGINX Plus fixed | 37.3.0.1, 37.0.8.1 | 37.2.0.1, 37.0.7.1 | | F5 advisory | K000163926 | K000163928 | F5's records mark NGINX Plus from R33 onward as affected; Rapid7 says no fix is listed for Plus R34 to R36, so the route is an upgrade to the 37 line. On NGINX Open Source, only the 1.30 and 1.31 branches get fixed releases; older versions are fixed only where a Linux distribution backports the patch (see below). The same release fixed eight other CVEs, among them a resolver use-after-free (CVE-2026-123634), an HTTP/3 use-after-free (CVE-2026-121810), a mail proxy use-after-free (CVE-2026-113425) and an infinite loop reading request bodies over TLS 1.3 (CVE-2026-118899), per [nginx.org](https://nginx.org/). Those do not depend on HTTP/2, which is why "we do not use HTTP/2" is not a reason to skip the upgrade. ## How hard is this to exploit? For CVE-2026-123007, [Rapid7](https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/) says its proof of concept needs roughly 128 GB of HTTP/2 traffic on a single connection and relies on CPU and C library behaviour that not every server has, and that it is unlikely to work through an intermediate proxy. [Wiz](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities) says it demonstrated CVE-2026-123007 against NGINX serving static files over HTTPS, and CVE-2026-123633 against a reverse proxy; [BleepingComputer](https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/) describes the first as unauthenticated code execution "on a server hosting ordinary static files over HTTP/2 with TLS", and reports that Wiz is not releasing its exploits for now. The honest summary: a crash is the likelier outcome on most systems, code execution is demonstrated in labs, and the bar will fall now that one exploit is public. ## Container escape to host root (Xint) **What was shown.** [Xint](https://xint.io/blog/nginx2root-remote-code-execution) says that "in our tests, the chain also escaped a Docker container running nginx and obtained root on the underlying host". The chain pairs CVE-2026-123007 with what Xint calls "a zero-day vulnerability" in the Linux kernel's SCTP subsystem: a use-after-free or double free in the SCTP send path that Xint says has been in the kernel since Linux 4.15 (2018). [BleepingComputer](https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/) reported the same on 19 November. This is a **researcher demonstration, not a reported incident**: no source we read reports it being used in an attack. **What is not known yet.** The kernel flaw has no CVE ID in any source we read, and Xint says it is withholding most details "until a kernel patch is available", so there is no fixed kernel version to install yet. Xint does not describe its Docker settings (seccomp profile, capabilities, privileged or not). **Conditions, as Xint states them.** "On many Linux distributions, the SCTP module is installed by default and the kernel loads it automatically the first time a program opens an SCTP socket." Whether SCTP is reachable "still depends on the kernel, the available modules, and the container's restrictions". Because every container shares the host kernel, a kernel compromise gives control of the host and every container on it. **What defenders should do:** - Patch NGINX first. The chain starts with CVE-2026-123007; without code execution in the NGINX worker there is nothing to chain. - Block the sctp module where you do not use SCTP (most web hosts do not; telecom signalling and some clustering software do). Xint's interim step, with its own caveats: `# Xint's interim step for hosts that do not use SCTP (run on the HOST, not in a container). # Is the module loaded right now? lsmod | grep -w sctp # Stop it being auto-loaded through modprobe: echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf # Per Xint, this does not unload a module that is already loaded (reboot or unload it), # and it does nothing if SCTP is compiled into the kernel rather than built as a module.` - Patch the kernel when a fix ships. Watch your distribution's kernel advisories for an SCTP fix credited to this research; until then, the module block is the control. - Keep containers constrained. Run NGINX containers with the runtime's default seccomp profile (never seccomp=unconfined), never with --privileged, and with no added capabilities. These are general hardening steps that reduce kernel attack surface; Xint has not said whether any of them would have stopped its chain. ## How many servers are exposed Version counts overstate the risk. [Xint](https://xint.io/blog/nginx2root-remote-code-execution) found that 98.9% of Shodan-indexed NGINX hosts showing a recognisable version were in CVE-2026-123007's affected range, but says "these numbers are based on reported version strings and don't confirm that a server is vulnerable": exploitation also needs HTTP/2, and a reported version may already include a backported fix. Censys estimated about 8.8 million services potentially exposed on 19 November from version numbers and HTTP/2 support, per [BleepingComputer](https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/), which also quotes researcher Florian Roth calling exposure claims based solely on version numbers "misleading". Configuration and distribution backports (see below) decide real exposure, so check your own servers rather than the headline count. ## Linux distribution packages - Ubuntu: [USN-9159-1](https://ubuntu.com/security/notices/USN-9159-1) (19 November 2026) fixes both HTTP/2 CVEs on every supported release from 16.04 ESM to 26.10. For Ubuntu 24.04 LTS the fixed source package is nginx 1.24.0-2ubuntu7.20; its changelog lists CVE-2026-123007 and CVE-2026-123633 alongside CVE-2026-113425, CVE-2026-118899 and CVE-2026-123634. - Debian: when we checked the [Debian security tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007), bookworm and trixie were still marked vulnerable to CVE-2026-123007, with a fixed package in unstable. Watch for a DSA. - Distro packages keep the upstream version number (1.24.0 stays 1.24.0), so compare the package version (dpkg -l 'nginx*', rpm -q nginx), not nginx -v. ## Timeline | Date | Event | Source | | --- | --- | --- | | 21 Oct 2026 | Wiz reports the use-after-free (later CVE-2026-123633) to F5 | Wiz | | 9 Nov 2026 | F5 reserves CVE-2026-123007 and CVE-2026-123633 | CVE.org | | 10 Nov 2026 | F5 shares a proposed patch with Wiz for review | Wiz | | 16-17 Nov 2026 | Wiz reports the flow-control flaw; F5 confirms it matches CVE-2026-123007 | Wiz | | 18 Nov 2026 | nginx 1.30.7 and 1.31.9 released with ten security fixes; F5 publishes the CVE records and advisories | nginx.org, CVE.org | | 18 Nov 2026 | Rapid7 and Wiz publish write-ups; Rapid7 releases a proof of concept for CVE-2026-123007 | Rapid7, Wiz | | 18 Nov 2026 | Canadian Centre for Cyber Security issues advisory AV26-1174 | CCCS | | 18 Nov 2026 | CISA's SSVC entry on both CVE records: Exploitation none, Technical impact total; neither CVE added to KEV | CVE.org, CISA KEV | | 18 Nov 2026 | Xint publishes NGINX2Root and says it chained CVE-2026-123007 with an unpatched Linux kernel SCTP flaw to escape a Docker container to host root (demonstration) | Xint | | 19 Nov 2026 | Ubuntu publishes USN-9159-1 with fixed nginx packages | Ubuntu | | 19 Nov 2026 | BleepingComputer reports the Wiz and Xint demonstrations; Censys estimates about 8.8 million potentially exposed services by version, which Florian Roth calls misleading | BleepingComputer | ## What security leaders should do this week - Inventory every NGINX. Web servers, reverse proxies, load balancers, Kubernetes ingress, container base images and appliances that embed NGINX. Ask vendors of anything you do not build whether they ship an affected build and when they will patch. - Find out where HTTP/2 is actually on. A compiled-in module is not the same as an enabled one: `# 1. Which version, and is the HTTP/2 module compiled in? nginx -v nginx -V 2>&1 | grep -o http_v2_module # 2. Is HTTP/2 switched on anywhere in the loaded config (listen ... http2, or "http2 on;" on 1.25.1+)? sudo nginx -T 2>/dev/null | grep -n http2 # 3. From outside: what does the server actually negotiate? curl -sS -o /dev/null --http2 -w '%{http_version}\n' https://your-host.example/` - Patch internet-facing HTTP/2 first. Upgrade to 1.30.7 or 1.31.9, NGINX Plus 37.3.0.1 or 37.0.8.1, or your distribution's fixed package. Rebuild container images; a patched package that never made it into the running image changes nothing. After reload, confirm old worker processes have exited. - If you cannot patch at once, turn HTTP/2 off on exposed listeners. F5 lists no workaround; Wiz suggests this stopgap and says to re-enable HTTP/2 after upgrading: `# Stopgap from Wiz, only until you can upgrade. Then re-enable HTTP/2. # nginx 1.25.1 and later, in each affected server block: http2 off; # All versions: remove the http2 parameter from listen, e.g. # listen 443 ssl http2; -> listen 443 ssl; # Then test and reload: sudo nginx -t && sudo systemctl reload nginx` - Close the container-escape path. Block the sctp kernel module on hosts that do not use SCTP, keep default seccomp and never run NGINX containers privileged (see [Container escape to host root](#container-escape)). - Patch the HTTP/1.1-only servers too. They are out of reach of these two CVEs, but the same release fixed resolver, mail proxy, HTTP/3 and TLS 1.3 flaws. - Watch for warning signs. Wiz suggests reviewing unexpected NGINX worker crashes (in the error log they appear as a worker process exiting on a signal) and commands spawned by NGINX processes, and notes that very long-lived HTTP/2 connections moving large volumes of data may point at CVE-2026-123007. It says these are general signs, not confirmed indicators. - Set the deadline with data. Check both CVEs in the [KEV checker](/tools/kev-checker) and [EPSS lookup](/tools/epss-lookup), run them through the [SSVC calculator](/tools/ssvc-calculator), and rank them against the rest of the queue with the [vulnerability prioritizer](/tools/vulnerability-prioritizer). Re-check KEV daily: a public proof of concept is often the step before a listing. - While you are in the config, confirm your edge still sends the headers you expect with the [security headers checker](/tools/security-headers-checker), and log any server you cannot patch this week in your risk register with an owner and a date. ## F5 in the Breach Index These CVEs are product vulnerabilities, not a breach of F5. Our [F5 Breach Index entry](/breach-index/f5) keeps them apart from the 2025 incident in which a nation-state actor stole BIG-IP source code. ## Frequently asked questions ### What are CVE-2026-123007 and CVE-2026-123633? Two memory-safety flaws in the NGINX HTTP/2 module (ngx_http_v2_module), fixed by nginx 1.30.7 (stable) and 1.31.9 (mainline) on 18 November 2026. CVE-2026-123007 is a flow-control window overflow (CWE-191 integer underflow, CWE-787 out-of-bounds write) that nginx.org rates "major". CVE-2026-123633 is a use-after-free (CWE-416) that nginx.org rates "medium". F5, which assigned both, scores each CVSS 3.1 8.1 and CVSS 4.0 9.2, and says both can crash a worker process or, where ASLR is disabled or can be bypassed, let an unauthenticated remote attacker run code. ### Am I affected if HTTP/2 is not enabled? Not by these two CVEs, according to the sources. F5's record for CVE-2026-123007 says it affects "configurations that use HTTP/2", and the record for CVE-2026-123633 says NGINX must be "configured to use HTTP/2 for client connections". Wiz says both require HTTP/2 to be enabled. Having the http_v2_module compiled in is not the same as using it: check the loaded config with nginx -T | grep http2. Other CVEs fixed in the same release, such as the resolver use-after-free CVE-2026-123634, do not depend on HTTP/2, so upgrade anyway. ### Which versions of NGINX fix the HTTP/2 RCE? NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). nginx.org lists 1.9.5 to 1.31.8 as vulnerable to CVE-2026-123007 and 1.19.7 to 1.31.8 as vulnerable to CVE-2026-123633. For NGINX Plus, F5's CVE records list fixes in 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, and mark R33 and later releases before the 37 line as affected; Rapid7 says no fix is listed for Plus R34 to R36. If you run Plus, move to 37.3.0.1 or 37.0.8.1, which are at or above both fixes. ### Is there a workaround? F5's CVE records list the workaround as "None". Wiz says that if you cannot upgrade at once, disabling HTTP/2 on affected instances removes the condition both flaws need: "http2 off;" on nginx 1.25.1 and later, and removing the http2 parameter from listen directives, then reload and confirm the old workers have exited. Treat that as a stopgap and re-enable HTTP/2 after upgrading. ### Is the NGINX HTTP/2 vulnerability being exploited? No in-the-wild exploitation was reported when we checked on 19 November 2026. Neither CVE is in the CISA Known Exploited Vulnerabilities catalog (version 2026.11.18), and CISA's SSVC entry on both CVE records, dated 18 November, says Exploitation: none. Rapid7 has published a proof of concept for CVE-2026-123007; Wiz says it built exploits for both and is not releasing them. A public proof of concept raises the chance of exploitation, so do not wait for KEV. ### How hard is CVE-2026-123007 to exploit? Rapid7, which published the proof of concept, describes heavy preconditions: roughly 128 GB of HTTP/2 data over one connection, a technique tied to particular CPU and C library behaviour, and little chance of working through an intermediate proxy. It says other methods may exist but none are known. A crash (denial of service) is the more likely outcome on most systems, but F5 rates the impact as possible code execution, so patch on that basis. ### Do Ubuntu and Debian have fixed nginx packages? Ubuntu published USN-9159-1 on 19 November 2026 covering both HTTP/2 CVEs, with fixed packages for every supported release; for Ubuntu 24.04 LTS the fixed source package is nginx 1.24.0-2ubuntu7.20, and its changelog names CVE-2026-123007 and CVE-2026-123633. When we checked, Debian's security tracker still showed bookworm and trixie as vulnerable to CVE-2026-123007, with a fix in unstable. Distro packages backport the fix, so the upstream version number (for example 1.24.0) stays the same: compare package versions, not nginx -v. ### What is NGINX2Root? The name the research firm Xint gave, in its own post on 18 November 2026, to five critical NGINX CVEs fixed that day, including these two HTTP/2 flaws. F5 and nginx.org do not use the name. The same release fixed ten CVEs in total; the two in this post are the ones in the HTTP/2 module. ### Can the NGINX HTTP/2 flaw lead to host root? In a researcher demonstration, yes; no such attack has been reported. Xint says it chained CVE-2026-123007 with a separate, still unpatched Linux kernel flaw in the SCTP subsystem to escape a Docker container running NGINX and get root on the host, and BleepingComputer reported the same on 19 November 2026. Xint has not given the kernel flaw a CVE ID, is withholding the details until a kernel patch exists, and does not describe the Docker settings it used. It says SCTP reachability depends on the kernel, the available modules and the container's restrictions, and that on many distributions the SCTP module is installed and loads automatically the first time a program opens an SCTP socket. Patch NGINX, block the sctp module on hosts that do not use SCTP (install sctp /bin/false in /etc/modprobe.d), keep the default seccomp profile and never run NGINX containers privileged. ### How many NGINX servers are exposed? Nobody knows precisely, and version-based counts overstate it. Censys estimated about 8.8 million services potentially exposed to CVE-2026-123007 on 19 November, from version numbers and HTTP/2 support, per BleepingComputer; Xint found 98.9% of hosts showing a recognisable version string in the affected range. Xint itself says such numbers "don't confirm that a server is vulnerable", because exploitation needs HTTP/2 and a reported version may already include a distribution's backported fix. Researcher Florian Roth told BleepingComputer that exposure claims based only on version numbers are misleading. ## Sources - [nginx.org: nginx security advisories (CVE-2026-123007 "Memory corruption in HTTP/2 flow control", CVE-2026-123633 "Use-after-free in HTTP/2")](https://nginx.org/en/security_advisories.html) - [nginx.org news, 18 November 2026: nginx-1.30.7 stable and nginx-1.31.9 mainline released](https://nginx.org/) - [nginx.org: CHANGES-1.30 (changes with nginx 1.30.7, 18 Nov 2026)](https://nginx.org/en/CHANGES-1.30) - [CVE.org: CVE-2026-123007 (CNA F5; includes CISA ADP SSVC)](https://www.cve.org/CVERecord?id=CVE-2026-123007) - [CVE.org: CVE-2026-123633 (CNA F5; includes CISA ADP SSVC)](https://www.cve.org/CVERecord?id=CVE-2026-123633) - [F5 K000163926](https://my.f5.com/manage/s/article/K000163926), [F5 K000163928](https://my.f5.com/manage/s/article/K000163928) and [F5 K000164058 (out-of-band security notification, 18 November 2026)](https://my.f5.com/manage/s/article/K000164058): linked from nginx.org and the CVE records; these pages did not render for us, so we cite the CVE records for F5's wording. - [CISA Known Exploited Vulnerabilities catalog (version 2026.11.18: neither CVE listed)](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) - [Ubuntu USN-9159-1: nginx vulnerabilities (19 November 2026)](https://ubuntu.com/security/notices/USN-9159-1) - [Debian security tracker: CVE-2026-123007](https://security-tracker.debian.org/tracker/CVE-2026-123007) - [Canadian Centre for Cyber Security: F5 security advisory AV26-1174 (18 November 2026)](https://www.cyber.gc.ca/en/alerts-advisories/f5-security-advisory-av26-1174) - [Wiz Research: Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 (18 November 2026)](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities) - [Rapid7: CVE-2026-123007, critical NGINX HTTP/2 integer underflow leads to RCE (fixed) (18 November 2026)](https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/) - [Xint: NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching (18 November 2026; kernel SCTP chain and container escape)](https://xint.io/blog/nginx2root-remote-code-execution) - [BleepingComputer: Critical NGINX "NGINX2Root" bugs let attackers hijack servers (Bill Toulas, 19 November 2026)](https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/) - [Tenable: NGINX2Root FAQ (18 November 2026; secondary, used for its exploitation snapshot)](https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx)