Back to Blog

Security Alert: Critical NGINX HTTP/2 Vulnerability (CVE-2026-123007)

NetOz19 November 2026
Security Alert: Critical NGINX HTTP/2 Vulnerability (CVE-2026-123007)

Last updated: 19 November 2026. We will update this post as patches are released.

On 18 November 2026, F5 and the researchers at Xint and Wiz disclosed CVE-2026-123007, a critical vulnerability in NGINX's HTTP/2 support. An attacker who can reach an affected server over HTTPS can run code on it without logging in. It is rated 9.2 (Critical) under CVSS 4.0.

NGINX is one of the most widely used web servers and reverse proxies, so this affects a large number of sites, panels and applications.

Who needs to act

  • You run your own server (a VPS, dedicated server, colocation or anything you manage yourself) and it uses NGINX: check it now using the steps below, and patch or mitigate it.
  • You are on a NetOz managed service: you do not need to do anything. See Managed customers below.
  • You are not sure: contact us and we will help you check.

What the vulnerability is

The bug is in how NGINX tracks HTTP/2 flow control. When a stream is cancelled, NGINX returns the unsent data allowance to the connection without checking the HTTP/2 limit. A client can use this to push the connection's send window past its maximum. That leads to a negative buffer length and memory corruption when NGINX sends data.

The researchers showed that this can be turned into code execution:

  • No login or special setup is needed. A default configuration with HTTP/2 enabled, serving ordinary static files over HTTPS, is enough.
  • Code runs as the NGINX worker user. The researchers also chained it with a separate Linux kernel bug to gain root, including from inside a Docker container. Keep your kernel patched as well.
  • Normal access logs may show nothing. The attack uses HTTP/2 control frames, which are not logged as requests.

At the time of writing, there are no reports of exploitation in the wild and no public exploit code. Given how much detail has been published, we expect that to change, so please do not wait.

Affected versions

ProductAffectedFixed
NGINX Open Source1.9.5 to 1.31.8, with HTTP/2 enabled1.30.7 (stable), 1.31.9 (mainline)
NGINX PlusR33 to 37.0.0 range37.0.8.1, 37.3.0.1

Linux distributions often backport fixes without changing the main version number. On Debian, Ubuntu and similar systems, check your distribution's security notice rather than relying on nginx -v.

Debian patch status

We are tracking the Debian status on the Debian security tracker for CVE-2026-123007. As of 19 November 2026, no fixed Debian package has been released yet:

Debian releasePackage versionStatus
Debian 12 (bookworm)1.22.1-9+deb12u10Vulnerable, fix pending
Debian 13 (trixie)1.26.3-3+deb13u10Vulnerable, fix pending
forky (testing)1.30.6-3Vulnerable, fix pending
sid (unstable)1.30.6-4Vulnerable, fix pending

Until a fixed package is available, use the mitigation below. When Debian publishes a fix, update with:

sudo apt update && sudo apt install --only-upgrade nginx
sudo systemctl restart nginx

For other distributions, see your vendor's advisory: Ubuntu, Red Hat and SUSE.

How to check if your server is affected

Your server is affected if it runs a vulnerable NGINX version and has HTTP/2 enabled.

  1. Check the version:

    nginx -v
    
  2. Check whether HTTP/2 is turned on in your configuration:

    sudo nginx -T 2>/dev/null | grep -nE 'listen .*http2|http2 on'
    

    Any output means HTTP/2 is enabled somewhere.

  3. Confirm from outside that the site negotiates HTTP/2 (replace the hostname with yours):

    echo | openssl s_client -connect example.com.au:443 -alpn h2 2>/dev/null | grep ALPN
    

    ALPN protocol: h2 means HTTP/2 is on.

Mitigation if you cannot patch yet

The recommended workaround is to turn off HTTP/2 until a fixed package is installed. Sites keep working over HTTP/1.1, which is slightly slower on pages with many files.

  • NGINX 1.25.1 and later: set http2 off; in each affected server block, and remove http2 from any listen lines.
  • NGINX 1.9.5 to 1.25.0: remove http2 from your listen lines, for example change listen 443 ssl http2; to listen 443 ssl;.

Then test the configuration and restart NGINX:

sudo nginx -t && sudo systemctl restart nginx

A reload is not enough: existing HTTP/2 connections stay open on the old worker processes. Run the openssl check above again to confirm HTTP/2 is now off.

Turning off HTTP/2 also blocks a related HTTP/2 flaw disclosed at the same time (CVE-2026-123633). Several other NGINX vulnerabilities were disclosed together, affecting HTTP/3, the DNS resolver, the mail proxy and other modules. The workaround does not cover them, so updating NGINX is still the real fix.

Managed customers

If NetOz manages your server, hosting or application, you do not need to do anything.

  • We are reviewing every managed service that uses NGINX.
  • Where appropriate, we have already disabled HTTP/2 as a temporary mitigation until fixed packages are installed.
  • We are applying fixed packages as soon as Debian and other vendors release them, and will keep doing so as further fixes arrive.
  • We will contact you directly if a change affects your service, for example a brief restart.

This post will be updated as patches roll out.

Need help?

If you run your own server and would like us to check it, apply the mitigation or patch it for you, get in touch. If you would rather not handle updates like this yourself, our managed services include security patching.

References

Update log

  • 19 November 2026: First published. No fixed Debian package yet. HTTP/2 workaround recommended, and HTTP/2 disabled on managed services where appropriate.

Need a hand with hosting or networking?

NetOz provides VM, managed and email hosting, DNS and colocation from a NextDC Tier IV facility in Adelaide.