Back to Blogs

Security8 min read

NGINX HTTP/2 Vulnerabilities CVE-2026-123007 and CVE-2026-123633: How to Check, Patch and Mitigate

NGINX HTTP/2vulnerabilities

On 18 November 2026, NGINX released fixes for two critical HTTP/2 vulnerabilities, CVE-2026-123007 and CVE-2026-123633. Both are rated CVSS 9.2 and can let an attacker who is not logged in run code on your web server. The flaws are in NGINX itself, not in your website or application, so a perfectly written app is still exposed if the NGINX in front of it has HTTP/2 enabled. Here is what each vulnerability does, how to check your servers in a few minutes, how to patch, and what to do if you cannot upgrade today.

Key takeaways

  • Patch: upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), then restart NGINX so the new binary is running.
  • NGINX Plus: 37.0.7.1 or 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 or 37.3.0.1 for CVE-2026-123007.
  • Can’t patch today? Turn HTTP/2 off (http2 off;) and reload. Both flaws need HTTP/2.
  • Static sites too: CVE-2026-123007 was shown on a server that only serves static files.
  • Containers and Kubernetes: rebuild from a patched base image and confirm the running image digest. The community ingress-nginx controller has no fixed image.

What are CVE-2026-123007 and CVE-2026-123633?

Both vulnerabilities sit in the code NGINX uses to handle HTTP/2 connections. They were found and reported by Wiz Research, and F5, which maintains NGINX, published the fixes alongside the NGINX security advisories.

  • CVE-2026-123007 is a memory-corruption bug in HTTP/2 flow control: an integer underflow in the send window. It affects any configuration with HTTP/2 enabled, including servers that only deliver static files and reverse proxies. Vulnerable versions run from NGINX 1.9.5 to 1.31.8.
  • CVE-2026-123633 is a use-after-free in HTTP/2 connection handling. It needs HTTP/2 enabled, NGINX proxying requests to an upstream (backend) server, and a worker process running low on available connections. Vulnerable versions run from NGINX 1.19.7 to 1.31.8.

F5 rates both at CVSS 9.2 (Critical). Wiz demonstrated unauthenticated remote code execution, meaning an attacker can send crafted HTTP/2 traffic and take control of the server process without any password or flaw in your application.

Is it being exploited?

By 19 November 2026 there were no confirmed reports of attacks in the wild, and the vulnerabilities were not yet in CISA’s Known Exploited Vulnerabilities catalogue. That window is unlikely to last: researchers have shown working exploits and demo videos are public. Hosting providers are taking it seriously too. DigitalOcean has warned customers running NGINX on Droplets, Kubernetes (DOKS), App Platform containers and Marketplace 1-Click images to upgrade immediately, and says it may restrict traffic to resources showing signs of compromise.

Who is affected?

You should treat yourself as affected until you have checked and upgraded if you run NGINX with HTTP/2 enabled anywhere you control it:

  • VPS and cloud servers (DigitalOcean Droplets, AWS EC2, Hetzner, Linode and similar).
  • NGINX as a reverse proxy or load balancer in front of Node.js, PHP, Python, Laravel or WordPress apps.
  • Docker containers built on an NGINX base image, including single-page apps served by NGINX.
  • Kubernetes clusters using an NGINX-based ingress controller.
  • Marketplace or one-click server images that ship NGINX.

If your site runs on a fully managed platform where you never operate the web server yourself, the provider is responsible for patching. It is still worth checking its status page, and checking whether any of your own containers include NGINX.

Affected and fixed versions

ProductVulnerable to CVE-2026-123007Vulnerable to CVE-2026-123633Fixed in
NGINX Open Source1.9.5 to 1.31.81.19.7 to 1.31.81.30.7 (stable) or 1.31.9 (mainline)
NGINX PlusR33 / 37.0.0 generationR33 / 37.0.0 generation37.0.8.1 or 37.3.0.1 for CVE-2026-123007; 37.0.7.1 or 37.2.0.1 for CVE-2026-123633

If you install NGINX from your Linux distribution’s packages, the version number alone may not tell you whether the fix is applied. Distributions often backport security patches to an older version number, and at the time of writing their patch status was uneven, so check your distribution’s security advisory for the package you run.

How to check if your NGINX server is vulnerable

Three quick checks, run on the server (or inside the container) that serves your traffic:

  1. Check the version. nginx -v prints the version. Anything below 1.30.7 on the stable branch, or below 1.31.9 on mainline, needs attention unless your distribution confirms a backported fix.
  2. Check whether HTTP/2 is enabled. sudo nginx -T prints the full configuration. Search it for http2:
sudo nginx -v
sudo nginx -T 2>/dev/null | grep -n "http2"

# HTTP/2 is enabled if you see lines such as:
#   listen 443 ssl http2;
#   http2 on;
  1. Confirm from outside. Ask curl which protocol the server agrees to. A result of 2 means HTTP/2. If your site sits behind a CDN, test the origin server directly, because the CDN may speak HTTP/2 to visitors while your origin does not, or the other way round.
curl -sI --http2 -o /dev/null -w "%{http_version}\n" https://your-domain.com

How to patch NGINX

The fix is to run a patched build: NGINX Open Source 1.30.7 or 1.31.9, or newer. How you get there depends on how NGINX was installed.

Servers using the official nginx.org packages

# Ubuntu / Debian
sudo apt update
sudo apt install --only-upgrade nginx

# RHEL / Rocky / AlmaLinux / Amazon Linux
sudo dnf upgrade nginx

# Alpine
sudo apk update && sudo apk upgrade nginx

# Then test the config, restart and confirm the version
sudo nginx -t
sudo systemctl restart nginx
nginx -v

If you use your distribution’s own NGINX package rather than nginx.org’s repository, run the same commands once your distribution has published its fix, and confirm against its security advisory rather than the version string.

Docker and container images

  1. Update the base image in your Dockerfile to a patched release, for example FROM nginx:1.30.7. A floating tag such as nginx:stable can still point at an old layer in your build cache, so pull fresh.
  2. Rebuild without cache, push and redeploy every service that uses the image.
  3. Confirm the running image digest, not just the tag label, and check nginx -v inside a running container.
docker pull nginx:1.30.7
docker build --no-cache -t your-app:patched .
docker exec <container> nginx -v

Kubernetes ingress controllers

If your cluster uses an NGINX-based ingress controller, update it to a release built on a patched NGINX. The community ingress-nginx project has been archived and had not published a fixed image at the time of writing, so disable HTTP/2 in its ConfigMap now and plan a move to a maintained controller (a supported NGINX Ingress Controller build or a Gateway API implementation):

apiVersion: v1
kind: ConfigMap
metadata:
  name: ingress-nginx-controller
  namespace: ingress-nginx
data:
  use-http2: "false"

If you cannot update today: disable HTTP/2

Both vulnerabilities need HTTP/2, so switching it off removes the attack path while you test and stage the upgrade. Visitors will not notice anything other than a small speed difference, because browsers fall back to HTTP/1.1 automatically.

  1. On NGINX 1.25.1 or later, add http2 off; to each affected server block.
  2. On every version, remove the http2 parameter from listen directives.
  3. Test with sudo nginx -t, then reload with sudo nginx -s reload.
  4. Confirm the old worker processes have exited (for example with ps aux | grep nginx), so no worker is still running the vulnerable HTTP/2 state.
  5. Re-enable HTTP/2 only after you have upgraded and verified the new version.
server {
    # before:  listen 443 ssl http2;
    listen 443 ssl;
    http2 off;   # NGINX 1.25.1 and later
    ...
}

A CDN or web application firewall that terminates HTTP/2 in front of your server may reduce exposure, but it is not a substitute for patching: anyone who can reach the origin server directly can still speak HTTP/2 to it.

After patching: verify and review

  1. Run nginx -v on every server and container and record the result.
  2. Repeat the curl check on each origin to confirm the protocol you expect.
  3. Make sure staging, admin panels and forgotten test servers are patched too, not only production.
  4. Review access and error logs from 18 November onwards for worker crashes, unusual HTTP/2 traffic spikes or unexpected processes. If anything looks wrong, isolate the server and rotate credentials and API keys.
  5. Set up alerts for future NGINX releases so the next advisory is a routine update.

How Tegnol keeps client servers patched

Vulnerabilities like these are a reminder that your risk includes the software underneath your app, not just your own code. We build and run client products so that a critical advisory becomes a short, rehearsed update:

  • Infrastructure as code. Servers, containers and ingress configuration are defined in code, so a patched base image can be rebuilt and redeployed in minutes, with health checks and rollback.
  • Supported versions only. We run maintained releases of NGINX and avoid archived components, so a fix is always available.
  • Monitoring and alerts. Security advisories, image scanning and dependency alerts run on the systems we manage.
  • Defence in depth. Least-privilege access, firewalls, rate limiting and tested backups, so one server bug does not become a full breach.

Every Tegnol project includes 30 days of free post-launch bug support, so if an advisory like this lands in that window, we patch, rebuild and redeploy at no extra cost. Small businesses on our Managed Websites plan get hosting, security updates and monitoring handled for them all year. If you want a second pair of eyes on your stack, our security and reliability review checks servers, containers and dependencies and gives you a prioritised fix list. You can also read what happens during a security audit.

Sources and further reading

Keep reading

FAQs

Frequently asked questions

NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026, fix both. For NGINX Plus, CVE-2026-123633 is fixed in 37.0.7.1 and 37.2.0.1, and CVE-2026-123007 in 37.0.8.1 and 37.3.0.1, or any newer release.

Still have questions? Email our team.