NGINX HTTP/2 CVE-2026-123007 (NGINX2Root): Fixed Versions

On November 18, 2026, nginx 1.31.9 mainline fixed ten vulnerabilities. nginx 1.30.7 stable fixed the nine that affect the stable branch. The most serious, CVE-2026-123007, is a memory corruption flaw in HTTP/2 flow control. F5 says it can let a remote attacker crash an nginx worker process, corrupt its memory or potentially run code. F5 lists nginx 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 as vulnerable in configurations that use HTTP/2.

Find your fixed version
By CalMax Systems Security Research · Published November 19, 2026 · Last updated: November 19, 2026

What is CVE-2026-123007, and which version fixes it?

CVE-2026-123007 is a flaw in nginx’s HTTP/2 flow control. F5 scores it 8.1 under CVSS 3.1 and 9.2 (Critical) under CVSS 4.0, and nginx.org rates it major. Upgrade nginx to 1.30.7 (stable) or 1.31.9 (mainline), or NGINX Plus to 37.3.0.1 or 37.0.8.1. A second HTTP/2 flaw, CVE-2026-123633, a use-after-free, has the same F5 scores and is fixed in the same nginx releases.

As of November 19, 2026, none of the ten CVEs in this release is in CISA’s Known Exploited Vulnerabilities catalog (version 2026.11.18). Xint, Wiz and Rapid7 each built working exploits for CVE-2026-123007 in their labs, and Rapid7 has published proof-of-concept exploit code, linked from its write-up. No exploitation in the wild has been reported in the sources we checked. F5 lists no mitigation for either HTTP/2 flaw, so upgrading is the fix. Until then, Xint, Wiz and Red Hat recommend temporarily disabling HTTP/2 (see below).

Fixed Versions for CVE-2026-123007

From nginx.org’s security advisories and F5’s advisory K000163926 (published November 18, 2026). Find the row for the product and branch you run.

Product Vulnerable Upgrade to
nginx Open Source, mainline1.31.0 through 1.31.81.31.9 or later
nginx Open Source, stable1.30.0 through 1.30.61.30.7 or later
Older nginx Open Source1.9.5 through 1.29.xNo fix on older branches. nginx.org lists only 1.30.7+ and 1.31.9+ as not vulnerable.
NGINX Plus37.1.0 through 37.2.0.1; 37.0.0 through 37.0.7.137.3.0.1 (CR track) or 37.0.8.1 (LTS track)
R34 through R36 (F5 advisory), plus R33 (CVE record)No fixed build is listed for these branches. Upgrade to a fixed NGINX Plus release. If upgrading from R36, first install R36 P8 and follow F5’s configuration preparation steps before moving to either fixed PLS.37 track.
NGINX Instance Manager2.19.0 through 2.24.12.25.0. Direct upgrades are supported from 2.22.0 through 2.24.1. For older releases, follow the supported upgrade path through an intermediate version.
F5 WAF for NGINX5.9.0 through 5.16.1, except the fixed 5.14.4 release5.16.2, or 5.14.4 on the 5.14 branch
NGINX App Protect WAF5.4.0 through 5.8.0; 4.12.0 through 4.16.0No fix listed
F5 DoS for NGINX4.8.0 through 4.12.04.13.0 with NGINX Plus 37.0.8.1 LTS, or 4.14.0 with NGINX Plus 37.3.0.1 CR. Update F5 DoS and NGINX Plus together. On Alpine 3.21, use the LTS pair or upgrade the OS before moving to the CR pair.
NGINX App Protect DoS4.5.0 through 4.7.0No fix listed
NGINX Gateway Fabric2.0.0 through 2.8.12.9.0
1.5.0 through 1.6.2No fix listed on 1.x. Follow the 1.x-to-2.x migration guide to move to 2.9.0. Uninstall the existing NGINX Gateway Fabric CRDs and deployment, then perform a fresh installation. Leave the Kubernetes Gateway API CRDs in place. Expect brief downtime.
NGINX Ingress Controller2026-lts-r1 through 2026-lts-r102026-lts-r11
5.0.0 through 5.7.15.8.0
4.0.0 through 4.0.1; 3.7.1 through 3.7.2No fix listed
BIG-IP (all modules), BIG-IQ, F5OS, F5 Insight, BIG-IP CNF, BIG-IP Next for Kubernetes, F5 AI GatewayNot vulnerableNo action needed
F5 Distributed Cloud, NGINX One ConsoleF5 is still researchingCheck K000163926 for updates
One upgrade covers the whole release. nginx 1.31.9 fixes all ten CVEs from November 18, and 1.30.7 fixes the nine that affect the stable branch (CVE-2026-120993 only affects mainline 1.31.4 through 1.31.8). For NGINX Plus, F5 lists 37.3.0.1 (CR track) and 37.0.8.1 (LTS track) for CVE-2026-123007. For the other nine it lists the same or earlier builds (for example 37.2.0.1 and 37.0.7.1 for CVE-2026-123633, and only the CR track for CVE-2026-120993), so either build covers the whole release on its track. The rows for NGINX Instance Manager, F5 WAF for NGINX, F5 DoS for NGINX, NGINX Gateway Fabric and NGINX Ingress Controller are the same in all ten F5 advisories. F5 Distributed Cloud and NGINX One Console are listed as not vulnerable in four of the advisories and still under research in the other six. F5 evaluates only versions that have not reached End of Technical Support.

Linux distribution packages (checked November 19, 2026)

Distributions often backport the fix into their own package, so the version nginx -v prints may not change. Compare the full package version with your distribution’s tracker. For CVE-2026-123007 and CVE-2026-123633:

  • Ubuntu: fixed in 1.28.3-2ubuntu1.13 (26.04 LTS), 1.24.0-2ubuntu7.20 (24.04 LTS), 1.18.0-6ubuntu14.23 (22.04 LTS) and 1.30.4-7ubuntu1.2 (26.10). Through Ubuntu Pro: 1.18.0-0ubuntu1.7+esm5 (20.04 LTS), 1.14.0-0ubuntu1.11+esm6 (18.04 LTS) and 1.10.3-0ubuntu0.16.04.5+esm11 (16.04 LTS, via the Legacy Support add-on). Ubuntu also lists its 1.18.0 and older packages (16.04 through 22.04) as needing the CVE-2026-123633 fix, even though the upstream range starts at 1.19.7. Its notes say only cleartext HTTP/2 listeners (listen ... http2 without TLS) are exposed on those releases, which the TLS check in step 4 below does not test.
  • Debian: fixed in 1.26.3-3+deb13u11 for Debian 13 (DSA-6642-1, which covers nine of the ten CVEs; CVE-2026-120993 only affects mainline) and in 1.30.6-4 for unstable. Debian 12 (bookworm) was still listed as vulnerable when we checked.
  • Red Hat: rates both flaws Critical. On November 19 it listed these as affected, with no fixed package yet: nginx in RHEL 10, the nginx package and the nginx:1.24 and nginx:1.26 module streams in RHEL 9, the nginx:1.24 stream in RHEL 8, the APIcast gateway in Red Hat 3scale API Management Platform 2, and nginx in Red Hat Hardened Images.

For any other distribution, or for a product that bundles nginx, check that vendor’s security tracker.

What CVE-2026-123007 and CVE-2026-123633 Do

Both flaws are in nginx’s HTTP/2 module (ngx_http_v2_module). F5 says both are data plane issues with no control plane exposure.

CVE-2026-123007 is a flow control window overflow. F5 says that when nginx processes undisclosed traffic, “the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault.” Attackers can also run code on systems where Address Space Layout Randomization (ASLR) is disabled or can be bypassed. F5 classes it as CWE-191 (integer underflow). Xint says the code has been in nginx since HTTP/2 support arrived in 1.9.5 in 2015.

The researchers who found it say the attacker needs no login and no backend application. Wiz demonstrated remote code execution on official nginx 1.31.7 and 1.31.8 builds serving ordinary static files over HTTPS on 64-bit systems. Xint says commands run with the privileges of the nginx worker process. Rapid7 describes real limits on its own exploit: it needs about 128 GB of HTTP/2 traffic, which takes about 17 minutes over a 1 Gbit/s link, and links slower than about 300 Mbit/s cannot finish within nginx’s default one-hour connection lifetime. It also depends on a specific glibc memory-copy routine selected on CPUs with AVX-512 features. Rapid7 says alternative strategies may be viable, but none are currently known. Rapid7 has published this proof-of-concept exploit on GitHub; its notes say it is only suitable for a freshly started local Docker container and will likely fail against a server with multiple concurrent clients or with network proxying in place. Wiz adds that CDNs and WAFs that terminate HTTP/2 in front of nginx may block parts of an exploit, depending on the implementation.

CVE-2026-123633 is a use-after-free. F5 says it affects nginx configured “to use HTTP/2 for client connections and proxy client requests to a backend,” when the worker process “is running low on worker_connections.” F5 lists 1.19.7 through 1.30.6 and 1.31.0 through 1.31.8 as vulnerable. Wiz says it is more likely to be exploited when nginx works as a reverse proxy.

Why “NGINX2Root”: Xint chained CVE-2026-123007 with a separate flaw it found in the Linux kernel’s SCTP subsystem and got root on the host. In its tests the chain also escaped a Docker container running nginx. Xint says it is withholding most kernel details until a kernel patch is available.

How many servers? Xint counted 56.7 million hosts for product:nginx on Shodan on November 10, 2026. Of the 11.94 million that reported a version, 98.9% fell in the 1.9.5 through 1.31.8 version range. That is a version-range estimate, not a count of vulnerable servers: Xint notes that HTTP/2 must also be enabled, and a reported version may already include a backported fix.

All Ten CVEs in the November 18 Release

Vulnerable ranges and severity from nginx.org; CVSS scores and mitigations from the matching F5 advisory. All are fixed in nginx 1.31.9, and all but the mainline-only CVE-2026-120993 in 1.30.7, even though nginx.org writes each range up to 1.31.8.

CVE What it is Vulnerable (nginx.org) nginx.org severity F5 CVSS 3.1 / 4.0 Mitigation F5 lists
CVE-2026-123007Memory corruption in HTTP/2 flow control1.9.5 to 1.31.8Major8.1 / 9.2None
CVE-2026-123633Use-after-free in HTTP/21.19.7 to 1.31.8Medium8.1 / 9.2None
CVE-2026-121810Use-after-free in HTTP/31.25.0 to 1.31.8Medium8.1 / 9.2None
CVE-2026-123634Use-after-free in the resolver0.6.18 to 1.31.8Medium8.1 / 9.2Avoid SSI or mirror directives, and avoid a proxied server name that contains variables
CVE-2026-118899Infinite loop while reading a client request body over TLS 1.31.13.0 to 1.31.8Major7.5 / 8.7None
CVE-2026-113425Use-after-free in the mail proxy module0.5.33 to 1.31.8Major8.1 / 9.2Restrict listeners to trusted networks
CVE-2026-120993NULL pointer dereference with PROXY protocol version 21.31.4 to 1.31.8 (mainline only)Minor5.3 / 6.9Turn off PROXY protocol v2 (proxy_protocol off; or v1 with proxy_protocol on;), or set both ssl_session_tickets off; and ssl_session_cache off;. Builds using BoringSSL or AWS-LC are not affected.
CVE-2026-125283Buffer overflow with alias and try_files0.9.6 to 1.31.8Minor5.3 / 6.9Use named regex captures instead of unnamed ones, and do not reuse a capture variable
CVE-2026-120967SNI bypass of client certificate validation in the stream module1.25.5 to 1.31.8Medium4.8 / 6.3Set ssl_verify_client on; in the default server of the shared listening socket, or give the server that requires client certificates its own address and port
CVE-2026-123640Insufficient validation in the stream ssl_preread module1.15.2 to 1.31.8Minor5.3 / 6.9Replace ssl_preread with TLS termination on nginx
Severity labels differ. nginx.org uses its own scale (minor, medium, major), while F5 publishes CVSS scores, so the two do not always agree: nginx.org rates CVE-2026-123633 medium, while F5 scores it 9.2 under CVSS 4.0. Several of these flaws only apply when a specific feature is in use, such as HTTP/3, the mail proxy, the resolver with variables or the stream module. The F5 advisory for each CVE gives the exact configuration.

How to Check Your Version and Exposure

These checks come from Xint’s write-up. Run them on each server that runs nginx.

1. Find the version

nginx -v 2>&1

F5 lists official releases 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 as vulnerable; 1.30.7 (stable) and 1.31.9 (mainline) or later are fixed. A distribution package can carry a backported fix under an older version number, so check the full package version against your distribution’s tracker (see the list above).

2. Check that the binary includes HTTP/2

nginx -V 2>&1 | grep -q -- '--with-http_v2_module' \
  && echo 'HTTP2_MODULE=present' || echo 'HTTP2_MODULE=absent'

Xint says a binary without the HTTP/2 module is not affected by CVE-2026-123007. The command also prints HTTP2_MODULE=absent if nginx is not on your PATH or fails to run, so make sure nginx -V works and that you are checking the binary your service actually starts.

3. Check whether HTTP/2 is turned on

sudo nginx -T 2>&1 | sed 's/#.*//' \
  | grep -nE 'listen[[:space:]].*http2|^[[:space:]]*http2[[:space:]]+on[[:space:]]*;'

Output such as http2 on; or listen 443 ssl http2; means HTTP/2 is enabled. No output means the filter found no matches. Review the full nginx -T output for the configuration your service uses, including directives split across lines, and confirm that the configuration test succeeds. nginx -T reads the configuration on disk, so a change that has not been reloaded may not match what is running.

4. Check whether HTTP/2 answers from the internet

From a machine outside your network, replace HOST with your hostname:

openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/null 2>&1 \
  | grep -E 'ALPN protocol:|No ALPN negotiated|Connection refused|connect:errno|handshake failure'

ALPN protocol: h2 confirms HTTP/2 on the tested hostname and port. Interpret No ALPN negotiated only after confirming the TLS handshake succeeded. Errors or empty output are inconclusive. Check reachability and inspect the unfiltered output if needed. Change the port if nginx does not listen on 443. For cleartext HTTP/2, review the full configuration as described in step 3. If a CDN or reverse proxy sits in front of nginx, this only tests the proxy, so run it against the nginx server directly as well.

5. HTTP/3 and the other features

CVE-2026-121810 applies to HTTP/3. Look for listen directives with the quic parameter and check the applicable http3 setting. HTTP/3 negotiation is enabled by default on a QUIC listener. Check for a UDP socket on each configured QUIC port, adjusting 443 as needed:

sudo ss -lunp 'sport = :443'

If the output shows nginx, it owns a UDP socket on that port. Match the address and port to an HTTP listen ... quic directive to distinguish it from another nginx UDP service. For the other CVEs, the F5 advisory linked from each row of the table above gives the exact configuration. In short, look for a mail block, resolver with a proxy_pass that contains variables, TLS 1.3 enabled, try_files with alias, and stream servers that use ssl_preread, ssl_verify_client or PROXY protocol v2.

nginx also ships inside other products. F5’s own NGINX-based products are in the table above. Ingress controllers, load balancers, appliances and container images from other vendors can bundle nginx too, and their version numbers may not match nginx’s. Check each vendor’s advisory for its fixed build.

Fixing It

F5 lists “Mitigation: None” for CVE-2026-123007, CVE-2026-123633, CVE-2026-121810 and CVE-2026-118899. Upgrading is the fix.

Upgrade, then restart

Install nginx 1.30.7 or 1.31.9, NGINX Plus 37.3.0.1 or 37.0.8.1, or your distribution’s fixed package. Xint notes that a configuration reload does not replace the running executable, so restart nginx or complete a supported live binary upgrade afterward. Confirm that the new processes are serving traffic and that the old master and workers have exited. Check the full installed package version for NGINX Plus and distribution builds. For F5’s NGINX-based products, install the fixed release from the table above using the product’s upgrade instructions. For Helm deployments of F5 NGINX Ingress Controller, update the CRDs before upgrading the chart. Use the 5.x upgrade guide for 5.8.0 or the LTS upgrade guide for 2026-lts-r11. If upgrading from 3.x, follow the custom resource migration instructions in the 5.x guide before applying newer CRDs.

Until you can upgrade: turn off HTTP/2 (researcher and Red Hat advice)

F5 lists no mitigation for the two HTTP/2 flaws. Xint, Wiz and Red Hat recommend temporarily disabling HTTP/2 on affected listeners until the fixed version is installed:

  • On nginx 1.25.1 and later, set http2 off; in each affected server block (replacing any http2 on;), and remove the http2 parameter from its listen directives. Xint says to check every server block that shares the same address and port.
  • On nginx 1.9.5 through 1.25.0, remove http2 from the listen directive, so listen 443 ssl http2; becomes listen 443 ssl;.
  • Validate and reload (the command below reloads only if validation succeeds), then verify each affected listener. For TLS, repeat step 4 above and confirm that HTTPS still works without negotiating h2. For cleartext, verify that HTTP/2 is disabled in the configuration applied to that listener.
sudo nginx -t && sudo nginx -s reload

A reload applies only to new connections. Xint says workers still shown as “worker process is shutting down” keep the old configuration, so restart nginx if they do not exit, and expect a short interruption. Wiz also says to confirm that the old workers have exited and to turn HTTP/2 back on after upgrading.

The trade-off: clients that support HTTP/1.1 keep working, but Xint warns that services that need HTTP/2, such as native gRPC, will be affected. Wiz advises testing application compatibility first.

What it does not cover: this blocks only CVE-2026-123007 and CVE-2026-123633. It does nothing for the other eight CVEs. HTTP/3 is a separate path: for CVE-2026-121810, Xint recommends removing QUIC listeners (listen ... quic), setting http3 off; and replacing any Alt-Svc header that advertises HTTP/3 with add_header Alt-Svc 'clear' always; until you patch. Validate and reload the configuration, then use the ss check in step 5 on each affected UDP port to verify that the QUIC sockets have closed. F5 lists no mitigation for that CVE either.

Feature-specific mitigations from F5

For six of the ten CVEs, F5 lists a configuration change for servers that cannot upgrade yet. They are in the last column of the table above. Each one covers only its own CVE, and none of them covers either HTTP/2 flaw.

Check for Signs of Compromise

Neither F5 nor nginx.org has published indicators of compromise. These are the signs the researchers describe.

What to look for

If you find activity you cannot explain, start your incident response process, preserve logs and core dumps before making changes, and patch.

Timeline

DateEvent
October 11, 2026Xint finds the vulnerabilities, according to its timeline.
October 16, 2026Xint reports them to F5 through HackerOne.
October 21, 2026Wiz reports CVE-2026-123633 to F5, which says another team had already reported it.
November 10, 2026F5 sends Wiz a patch for CVE-2026-123633 to review. Xint finishes validating the patches.
November 12, 2026Rapid7 discloses CVE-2026-123007 to F5.
November 16, 2026Wiz reports CVE-2026-123007 to F5. F5 confirms to Rapid7 its validation of the vulnerability, the CVE assignment and a November 18 disclosure date.
November 17, 2026F5 confirms to Wiz that its report matches CVE-2026-123007 and is included in the planned November 18 security release.
November 18, 2026nginx 1.30.7 and 1.31.9 are released. F5 publishes its advisories, the CVE records go live, and Xint, Wiz and Rapid7 publish their research. Rapid7 also publishes proof-of-concept exploit code on GitHub. CISA’s assessment in the CVE records lists exploitation as none.
November 19, 2026None of the ten CVEs is in CISA’s Known Exploited Vulnerabilities catalog (version 2026.11.18).

Where ThreatListPro Fits

A blocklist does not fix this flaw. Patching does.

An unauthenticated client that can reach an affected nginx HTTP/2 listener can attempt to exploit CVE-2026-123007. No list of known attacker addresses can stop a new address from sending the attack. Upgrade nginx, or install the fixed package or product release.

ThreatListPro is built for a different job: keeping known VPN attackers away from your login pages. It covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Its entries come from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. A firewall deny rule that uses it can reduce scanning and login attempts from listed addresses on your VPN portal and other remote-access services. See how to block IP addresses at the firewall for the supported firewalls.

NGINX CVE-2026-123007 FAQs

What is NGINX2Root?

NGINX2Root is the name Xint gave to its findings: five nginx vulnerabilities led by CVE-2026-123007, an HTTP/2 flow control flaw, plus a separate Linux kernel flaw that Xint says can be chained with any of them to get root on the host. The five nginx CVEs are CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425. All five are fixed in nginx 1.30.7 and 1.31.9, released on November 18, 2026.

Which nginx version fixes CVE-2026-123007?

nginx 1.30.7 (stable) and 1.31.9 (mainline). F5 lists 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 as vulnerable. For NGINX Plus, F5 lists 37.3.0.1 (CR track) and 37.0.8.1 (LTS track) as the fixed builds. The CVE record lists R33 as affected, and the F5 advisory lists R34 through R36. Upgrade to a fixed build. Distribution packages often backport the fix without changing the version that nginx -v prints, so check your distribution's security tracker.

Is CVE-2026-123007 being exploited?

No exploitation in the wild has been reported in the sources we checked. As of November 19, 2026, CVE-2026-123007 is not in CISA's Known Exploited Vulnerabilities catalog (version 2026.11.18), and the CISA assessment in the CVE record lists exploitation as none. Exploit code is public, though: Rapid7's write-up links to its proof-of-concept exploit on GitHub, which Rapid7 says demonstrates unauthenticated remote code execution against a vulnerable nginx 1.31.8 Docker container. Wiz says it will not release its exploits for now, and Xint left the final steps out of its write-up.

Am I affected if HTTP/2 is not enabled?

Not by CVE-2026-123007 or CVE-2026-123633. F5 says CVE-2026-123007 affects configurations that use HTTP/2, and CVE-2026-123633 affects configurations that use HTTP/2 for client connections and proxy requests to a backend. The same release fixes eight other flaws in HTTP/3, the resolver, TLS 1.3 request bodies, the mail proxy, try_files with alias and the stream module, so upgrade even if HTTP/2 is off.

Is there a workaround for CVE-2026-123007?

F5 lists Mitigation: None for CVE-2026-123007 and CVE-2026-123633, and the fix is upgrading to nginx 1.30.7 or 1.31.9, or to NGINX Plus 37.3.0.1 or 37.0.8.1. Until you can upgrade, Xint, Wiz and Red Hat recommend temporarily disabling HTTP/2 on affected listeners: set http2 off; (nginx 1.25.1 and later) and remove the http2 parameter from listen directives, then validate and reload. Wiz says to test application compatibility first and to confirm the old workers have exited after the reload. Xint warns that services that need HTTP/2, such as native gRPC, will be affected. This covers only the two HTTP/2 flaws, not the other eight CVEs in the release.

What are the CVSS scores for CVE-2026-123007 and CVE-2026-123633?

F5 scores both 8.1 (High) under CVSS 3.1 and 9.2 (Critical) under CVSS 4.0. nginx.org rates CVE-2026-123007 major and CVE-2026-123633 medium. Both are network attacks that need no authentication, and F5 rates their attack complexity high.

Are F5 BIG-IP and other F5 products affected?

F5 lists BIG-IP (all modules), BIG-IQ, F5OS and F5 AI Gateway as not vulnerable. Products built on NGINX are affected, including NGINX Instance Manager, F5 WAF for NGINX, F5 DoS for NGINX, NGINX Gateway Fabric and NGINX Ingress Controller, and F5 lists fixed releases for each. F5 is still researching F5 Distributed Cloud and NGINX One Console.

Sources

Run a VPN Portal Too?

ThreatListPro blocks known VPN attackers at the firewall: 5.4M+ IPv4 addresses, checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial Or test the free sample first: free, no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

Other internet-facing flaws we track, and how to block known attackers at the edge.

All Security Alerts OpenSSH CVE-2026-123158: Who Is Affected? F5 BIG-IP November 2026 Security Update Block an IP Address at the Firewall VPN Brute Force Explained Password Spraying on VPNs