
The nginx project released nginx 1.30.7 (stable) and nginx 1.31.9 (mainline) on 18 November 2026, fixing ten vulnerabilities in one go. Five of them, grouped under the name NGINX2Root, are memory-safety bugs that an unauthenticated attacker can use to crash nginx worker processes. Under the right conditions they may also lead to code execution. The most serious one is in HTTP/2 support, which most HTTPS sites turn on. If you run nginx in front of websites, APIs or WordPress installs, schedule this update today rather than at your next maintenance window.
What was fixed
These are the ten issues listed in the nginx.org announcement:
| CVE | Area | Issue |
|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control | Memory corruption |
| CVE-2026-123633 | HTTP/2 | Use-after-free |
| CVE-2026-121810 | HTTP/3 | Use-after-free |
| CVE-2026-123634 | Resolver | Use-after-free |
| CVE-2026-113425 | Mail proxy module | Use-after-free |
| CVE-2026-118899 | Request body over TLS 1.3 | Infinite loop |
| CVE-2026-120993 | PROXY protocol v2 | NULL pointer dereference |
| CVE-2026-125283 | alias with try_files | Buffer overflow |
| CVE-2026-120967 | Stream module client certificates | SNI bypass |
| CVE-2026-123640 | Stream ssl_preread | Insufficient validation |
According to AlmaLinux’s advisory, F5 scores each of the five NGINX2Root flaws 9.2 (Critical) under CVSS v4.0. The worst case is code execution as the nginx user, and it is most realistic where address space layout randomisation is disabled or has been bypassed.
Are you exposed?
Exposure depends on which features your configuration uses:
- CVE-2026-123007 (HTTP/2 flow control): any server with HTTP/2 enabled. Researchers reported working code execution against an ordinary HTTPS server that only serves static files.
- CVE-2026-123633 (HTTP/2): HTTP/2 on nginx 1.19.7 and later.
- CVE-2026-121810 (HTTP/3): HTTP/3 on nginx 1.25.0 and later.
- CVE-2026-123634 (resolver): proxying to server names that contain variables, combined with SSI or
mirrorsubrequests. - CVE-2026-113425 (mail proxy): only if you run nginx as a mail proxy.
The default nginx.conf does not turn on HTTP/2, but most HTTPS virtual hosts do. To check quickly:
sudo grep -RnE '^\s*(listen\s.*\bhttp2\b|http2\s+on)' /etc/nginx
If that prints nothing, HTTP/2 is off. If it prints anything, treat the server as exposed.
How to update
nginx.org packages or source builds
Move to 1.30.7 if you track stable, or to 1.31.9 if you track mainline. With the official nginx.org repository:
# Debian / Ubuntu
sudo apt update && sudo apt install --only-upgrade nginx
# RHEL / Rocky / AlmaLinux
sudo dnf upgrade nginx
nginx -v
sudo nginx -t && sudo systemctl restart nginx
Distribution packages
Distributions backport fixes, so the upstream version number does not change. On AlmaLinux 8, 9 and 10, fixed builds are already available. Check that you have them with rpm -q nginx, not nginx -v:
sudo dnf clean metadata && sudo dnf upgrade 'nginx*'
sudo systemctl restart nginx
rpm -q nginx
AlmaLinux notes that its retired module streams will not be patched. On AlmaLinux 8 that means nginx:1.14 (the default), 1.16, 1.18, 1.20 and 1.22; on AlmaLinux 9 it means nginx:1.22. If dnf module list nginx shows you on one of those, switch to a maintained stream such as nginx:1.24 and test your configuration. On Debian and Ubuntu, watch your distribution’s security tracker and apply the nginx update once it lands.
Restart, do not reload
A reload keeps the old binary in memory. A full systemctl restart nginx is the only way to load the patched code.
If you cannot patch today
Turning off HTTP/2 closes the two HTTP/2 flaws, but it does nothing for the other eight. Remove http2 from every listen line, or set http2 off; on builds that use the newer directive. You have to change every occurrence, because a single remaining http2 on a shared listen address keeps HTTP/2 enabled for every site on that address. Then test the config and restart:
sudo nginx -t && sudo systemctl restart nginx
curl -so /dev/null --http2 -w '%{http_version}\n' https://your-site.example/
The curl command should print 1.1. Browsers fall back to HTTP/1.1 without trouble, but gRPC proxying needs HTTP/2 and will break. Undo the change after you patch.
Quick checklist
- List every nginx instance, including control panel builds, containers and load balancers.
- Check which features each one uses: HTTP/2, HTTP/3, mail, stream, resolver.
- Update to 1.30.7, 1.31.9 or your vendor’s fixed package.
- Restart, then confirm the running version or package release.
- Rebuild and redeploy container images that bundle nginx.
How TechProvidence can help
We patch and harden nginx on managed Linux servers, cPanel/WHM hosts and container platforms, including staged rollouts with no downtime and moves off unsupported module streams. If you need a fleet audited or updated quickly, contact us.
Source: nginx.org


