CVE-2026-123007 and CVE-2026-123633: the nginx HTTP/2 RCE, who is affected and the fix

CVE-2026-123007 and CVE-2026-123633 are two memory flaws in the HTTP/2 code of nginx, disclosed on 18 November 2026, that can let a stranger run code on the server without an account. Both need HTTP/2 enabled. They affect nginx 1.9.5 to 1.31.8 and 1.19.7 to 1.31.8, and are fixed in 1.30.7 and 1.31.9. If you cannot upgrade today, turn HTTP/2 off.

The team behind Keybrum's attacksUpdated 9 min read
CVE-2026-123007NGINX2Rootcritical · CVSS 9.2
Component
nginx HTTP/2 module (ngx_http_v2_module)
Affected
nginx 1.9.5 to 1.31.8 with HTTP/2 enabled (CVE-2026-123633: 1.19.7 to 1.31.8, as a reverse proxy). NGINX Plus before 37.0.8.1 and 37.3.0.1
Fixed in
nginx 1.30.7, 1.31.9
Published
November 18, 2026
Exploited in the wild
No public report

In short

  • Affected: nginx 1.9.5 to 1.31.8 (CVE-2026-123007) and 1.19.7 to 1.31.8 (CVE-2026-123633), with HTTP/2 enabled. Fixed in 1.30.7 stable and 1.31.9 mainline, released on 18 November 2026.
  • F5 scores both 9.2 Critical (CVSS 4.0) and 8.1 High (CVSS 3.1). Neither is in CISA's KEV catalog as of 19 November 2026 and no attack has been reported. Rapid7 has published a proof of concept.
  • Ubuntu, Debian and Alpine patch without changing the nginx version: nginx/1.24.0 (Ubuntu) can be fixed or not. Compare the full package release with your distribution's advisory.
  • A CDN in front helps only when your server refuses connections that come around it. Every known exploit needs to talk to nginx directly.
  • No upgrade today: set http2 off;, remove http2 from every listen line, reload, and check that the old workers have exited.
On this page

What the two nginx flaws are, in plain words

nginx is the web server in front of a large share of the web: it handles HTTPS and forwards each request to the app behind it. HTTP/2 is the protocol browsers use to send many requests over one connection. On 18 November 2026, nginx released fixes for two memory bugs in its HTTP/2 code. Wiz, Xint, Rapid7 and two other teams found them independently, and Wiz describes both as unauthenticated remote code execution.

  • CVE-2026-123007, memory corruption in HTTP/2 flow control. nginx miscounts how much data it may still send, and a later copy goes outside its buffer. The code dates from nginx 1.9.5, released in 2015. Wiz ran code on a server that only served static files over HTTPS, with no app behind it.
  • CVE-2026-123633, a use-after-free in HTTP/2. nginx frees a connection while a request on it is still running. It needs nginx to forward requests to a backend, as a reverse proxy does, with a worker "running low on worker_connections", in F5's words.

Xint groups CVE-2026-123007 with four other flaws of the same release under the name NGINX2Root.

What a stranger can do

Run code on the machine as the nginx worker, with no account and no click from anyone. Wiz lists what follows: running commands, stealing data, changing pages, stopping services. One nginx often serves several apps, so one unpatched server can expose all of them. The bug is in nginx itself: a flawless app behind it is just as exposed.

Severity and exploitation status

SourceRatingDetail
F5, the CNA (CVSS 4.0)9.2 Critical, both CVEsAV:N/AC:H/AT:N/PR:N/UI:N: over the network, no account, no user action, high attack complexity
F5 (CVSS 3.1)8.1 High, both CVEsAV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nginx.orgmajor (123007), medium (123633)nginx's own scale, on its security advisories page
CISA KEVNot listedCatalog version 2026.11.18, 1,786 entries

No attack in the wild had been reported on 19 November. Rapid7 has published a proof of concept for CVE-2026-123007 and states its limits. The exploit sends about 128 GB of HTTP/2 data, which takes 17 minutes on a 1 Gbit/s link. Below about 300 Mbit/s it cannot finish, because nginx closes a connection after one hour by default. It also relies on one x86-64 glibc memory copy routine. Rapid7 adds that other ways to exploit it may be viable.

The exposure is wide. On 10 November, Xint counted 56.7 million nginx hosts on Shodan. Of the 11.94 million that show a version, 98.9% were in the range of CVE-2026-123007. That count reads version strings only: it does not tell HTTP/2 or distribution patches apart.

Who is affected

This page is about an nginx you run yourself: a VPS, a Docker setup, Coolify, a Kubernetes cluster. When a platform runs the web server for you, as Vercel, Netlify or Lovable do, patching it is the platform's job. Your server is exposed to CVE-2026-123007 when both of these are true:

  1. It runs nginx 1.9.5 to 1.31.8 without your distribution's fix, or NGINX Plus before 37.0.8.1 and 37.3.0.1.
  2. HTTP/2 is on: http2 on; in the config, or http2 on a listen line such as listen 443 ssl http2;.

CVE-2026-123633 needs nginx 1.19.7 or later, HTTP/2, requests forwarded to a backend (proxy_pass and the like), and a worker short of worker_connections. HTTP/2 is off unless a config turns it on (Default: http2 off; in the nginx docs), so look at your own config before you conclude anything.

SetupWhat applies
nginx from nginx.org or the official Docker imageAffected below 1.30.7 (stable) and 1.31.9 (mainline). The images nginx:1.30.7 and nginx:1.31.9, and their -alpine variants, were published on 18 and 19 November.
nginx from Ubuntu, Debian or AlpineThe version number does not change with the fix. Ubuntu 24.04: fixed in 1.24.0-2ubuntu7.20. Ubuntu 22.04: 1.18.0-6ubuntu14.23. Debian 13: 1.26.3-3+deb13u11. Debian 12: still listed as vulnerable on 19 November. Alpine 3.22 and 3.23: 1.28.3-r8. Alpine 3.24: 1.30.7-r0.
F5 NGINX Ingress Controller, NGINX Gateway Fabric, F5 WAF for NGINXAffected per F5's CVE records. Ingress Controller is fixed in 5.8.0, Gateway Fabric in 2.9.0, F5 WAF for NGINX in 5.16.2.
Community ingress-nginx on KubernetesThe project was archived in March 2026 and ships no fix. Move to a maintained controller.
Behind Cloudflare or another CDNThe CDN speaks HTTP/2 with visitors and opens its own connection to your server. Wiz writes that CDNs which terminate HTTP/2 "may mitigate parts of the exploit", and that any exploit needs a direct line to nginx. That holds only if your server refuses visitors who skip the CDN.

How to check your nginx

Check the version that actually runs. When nginx comes from your distribution, check the full package release as well.

bash
# The version of the nginx binary
nginx -v

# Docker: the version inside the running container, not the image you last pulled
docker exec <container> nginx -v

# Distribution packages: the full release, to compare with the advisory
dpkg -s nginx | grep Version    # Debian, Ubuntu
apk info -v nginx               # Alpine
rpm -q nginx                    # RHEL, Fedora, Amazon Linux

# Is HTTP/2 on? Look for http2 in the full config
nginx -T 2>/dev/null | grep -n http2
Run these on your own server.

Then check from outside, against your own server. Behind a CDN, call your server's IP address directly with your domain name. If it answers over HTTP/2, anyone who finds that address reaches the same nginx.

bash
# Your own domain, and your own server's IP address
curl -skI --http2 --resolve example.com:443:203.0.113.10 https://example.com/ \
  -o /dev/null -w '%{http_version}\n'
# 2: HTTP/2 straight to nginx. 1.1: HTTP/2 is off there. No answer: the origin is closed.
A self-test of your own origin.

The Server header gives a hint too: nginx/1.29.3 is in range, while nginx/1.24.0 (Ubuntu) says nothing about the patch. Hiding the version with server_tokens off; is good hygiene, as the security headers guide explains. It fixes nothing.

How to fix CVE-2026-123007 and CVE-2026-123633

  1. 1

    Upgrade nginx

    Go to 1.30.7 (stable) or 1.31.9 (mainline), or to your distribution's fixed package. NGINX Plus: 37.0.8.1 or 37.3.0.1. One release closes both CVEs and eight other nginx flaws. Older branches such as 1.28 get no upstream release.

  2. 2

    Restart what serves traffic

    A new package does nothing until the old workers exit. With Docker, set the new tag and recreate the container: a running container keeps its old image.

  3. 3

    Check again

    Run nginx -v inside what serves traffic, then the curl above.

bash
# Docker: set image: nginx:1.30.7-alpine (or 1.31.9) in compose.yaml, then
docker compose pull nginx
docker compose up -d --force-recreate nginx

# Ubuntu, Debian
sudo apt update && sudo apt install --only-upgrade nginx
sudo systemctl restart nginx

# Alpine
apk upgrade nginx && rc-service nginx restart
nginx
# Before
listen 443 ssl http2;

# Until the upgrade
listen 443 ssl;
http2 off;

What people miss after the upgrade

  • The container still runs the old image. Pulling downloads the new one. The running container changes only when it is recreated.
  • Ubuntu reports the same version before and after. Trust the package release, not nginx -v or the Server header.
  • The CDN is not a wall if the origin answers. Accept port 443 only from your CDN's published address ranges, or use a tunnel, so that nothing else reaches nginx. The attack surface guide covers the addresses that give an origin away.
  • Other builds of nginx. OpenResty, Kubernetes ingress controllers and appliances embed their own copy, and each needs its own release. OpenResty had no fixed release when we checked on 19 November.
  • The other fixes in the release. It also closes a use-after-free in HTTP/3 (CVE-2026-121810) and seven more flaws. The nginx changelog lists them.

Timeline

DateEvent
2015nginx 1.9.5 ships the code behind CVE-2026-123007.
21 October 2026Wiz reports the use-after-free, later CVE-2026-123633, to F5. F5 says another team reported it first.
10 November 2026F5 shares a patch for CVE-2026-123633 with Wiz for review.
16 November 2026Wiz reports the flow control bug, CVE-2026-123007.
18 November 2026nginx 1.30.7 and 1.31.9 released. F5, Wiz, Xint and Rapid7 publish, and NVD lists both CVEs the same day.
19 November 2026Neither CVE is in CISA's Known Exploited Vulnerabilities catalog.

How Keybrum watches your nginx

Keybrum's CVE watch reads the nginx version your server announces in its Server header: on your live address, and on the server behind your CDN once you prove you own the domain. Every hour, it matches that version against nginx.org's own advisory list, scored by NVD, and checks whether the server speaks HTTP/2. When CVE-2026-123007 or CVE-2026-123633 reaches it, you get an alert with the release to take, and your coding agent gets the upgrade plan over MCP. The advisory closes when your server announces a fixed release.

Two limits come from reading a version from outside. A server that hides its version with server_tokens off; cannot be matched: Keybrum keeps the last version it announced until it shows another, so hiding it closes nothing. A distribution can ship the fix under the same version number: when the alert names an Ubuntu or Debian build, check the package release. Keybrum never sends remote code execution payloads, so no attack fires these exploits at your server.

The free security headers checker runs the same match once, for any address. The React2Shell page shows the other half of the watch: the npm packages your app is built from.

Questions

Which nginx version fixes CVE-2026-123007 and CVE-2026-123633?

nginx 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026. NGINX Plus is fixed in 37.0.8.1 and 37.3.0.1 for CVE-2026-123007, and in 37.0.7.1 and 37.2.0.1 for CVE-2026-123633. Older branches such as 1.28 get no upstream release.

Is nginx 1.24.0 on Ubuntu affected by CVE-2026-123007?

It depends on the package release, not on the version. Ubuntu 24.04 fixed both flaws in 1.24.0-2ubuntu7.20, which still reports itself as 1.24.0. Run dpkg -s nginx | grep Version and compare.

Does turning off HTTP/2 fix CVE-2026-123007?

It removes the condition both flaws need, which is why Wiz gives it as the workaround. Set http2 off;, remove http2 from your listen lines, and reload. Upgrade anyway: the same release fixes eight other nginx flaws, some of them outside HTTP/2.

Does Cloudflare protect nginx from CVE-2026-123007?

Partly, and only if nobody can reach your server directly. Wiz writes that CDNs which terminate HTTP/2 may mitigate parts of the exploit, and Rapid7 writes that proxied HTTP/2 traffic will likely not carry it. If your server's IP address answers on port 443, the CDN is bypassed.

Is CVE-2026-123007 exploited in the wild?

No attack had been reported on 19 November 2026, and CISA has not added it to its Known Exploited Vulnerabilities catalog. Rapid7 has published a proof of concept, which needs about 128 GB of HTTP/2 traffic and a fast link to work.

Does Keybrum detect CVE-2026-123007?

Yes, from the version your server announces. Keybrum's CVE watch matches the nginx version in your Server header against nginx.org's advisory list every hour, on your live address and on the server behind your CDN for a verified domain. The free security headers checker does the same once, for any address. Keybrum never sends the exploit itself.

Sources

  1. 1.nginx security advisories, nginx.org
  2. 2.Changes with nginx 1.31.9, nginx.org
  3. 3.Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007, Wiz Research
  4. 4.CVE-2026-123007, NIST National Vulnerability Database
  5. 5.CVE-2026-123633, NIST National Vulnerability Database
  6. 6.CVE-2026-123007, CVE Program
  7. 7.CVE-2026-123007: Critical NGINX HTTP/2 integer underflow leads to RCE (fixed), Rapid7
  8. 8.NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching, Xint
  9. 9.CVE-2026-123007 in Ubuntu, Canonical
  10. 10.CVE-2026-123007 in Debian, Debian Security Tracker
  11. 11.Module ngx_http_v2_module, nginx.org
  12. 12.Known Exploited Vulnerabilities Catalog, CISA

Your app is public. So are its mistakes.

Check what any attacker can already see in it, free, in ten seconds. The full attack, with proof and fixes: €49 once, or €29 a month on a plan.

or continue with Google or GitHub