HostiServer
2026-11-19 10:54
NGINX2Root: nginx Vulnerabilities, Check and Update
NGINX2Root: Critical nginx Vulnerabilities (CVE-2026-123007 and Four More). How to Check Your Server and Update
On November 18, 2026, five critical vulnerabilities in the nginx web server were publicly disclosed under the collective name NGINX2Root: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425. They allow an unauthenticated attacker to execute code on the server with the privileges of the nginx worker process. Researchers also showed that these vulnerabilities can be chained with a separate, still unpatched Linux kernel vulnerability to obtain full root access to the server, including when nginx runs inside a Docker container.
Nginx is installed on a huge number of websites, reverse proxies, and ingress servers, so the chance that you have it too is very high. Below: who is affected, how to check your server in half a minute, how to update, and what to do if you can't update right now.
📩 We have already notified our clients. Hostiserver sent clients emails describing the issue and recommendations. If you received such an email, this article expands on it with practical commands. If you didn't receive one but nginx is on your server, assume the problem affects you too and follow the steps below.
🚨 Emergency steps: can't update? Here is what to do first:
- Disable HTTP/2 on all public nginx servers (section 4): this closes the most serious of the five vulnerabilities.
- If HTTP/3 (QUIC) is enabled, disable it too.
- Check the configuration with
nginx -tand restart nginx rather than just reloading it: reload keeps the old processes and long-lived HTTP/2 connections alive. - Schedule a full package update as soon as it appears in your repository.
1. Five Vulnerabilities: What Exactly Is Broken
| CVE | Where the Problem Is | When You Are at Risk |
|---|---|---|
| CVE-2026-123007 | Integer overflow in the HTTP/2 flow-control accounting, leading to out-of-bounds writes and reads in the heap buffer | All official nginx releases from 1.9.5 to 1.31.8 with HTTP/2 enabled: this is most HTTPS sites |
| CVE-2026-123633 | Use-after-free: an HTTP/2 connection remains available to be "freed" while a request opens a connection to the backend | HTTP/2 and proxying requests to an upstream (from 1.19.7) |
| CVE-2026-121810 | Use-after-free during HTTP/3 (QUIC) stream creation | HTTP/3 and proxying to an upstream (from 1.25.0) |
| CVE-2026-123634 | Use-after-free in the DNS resolver when a request and its mirrored subrequest wait for the same DNS response | The resolver directive, proxy_pass with a request-dependent address, and mirror with mirror_request_body off (from 1.13.4) |
| CVE-2026-113425 | Use-after-free in the mail proxy when interacting with auth_http |
The nginx mail proxy with auth_http (from 0.5.15) |
For the worst one, CVE-2026-123007, an externally reachable TLS port with HTTP/2 is enough, and the attacker needs no authentication. The other four affect specific configurations, but if your server runs nginx, you should consider it vulnerable until you update it.
Why This Is More Dangerous Than It Looks: The Kernel Chain
Separately, researchers found a vulnerability in the SCTP subsystem of the Linux kernel (present since version 4.15) that had not been patched at the time of publication. Chained with one of the nginx vulnerabilities, it gave them root access to the host. This matters especially for Docker: a container shares the kernel with the host, so compromising nginx in a container means control over the host and all the other containers on it (if SCTP is available). Many distributions automatically load the SCTP module when a program opens an SCTP socket.
2. How to Check Your Server in Half a Minute
2.1 nginx Version
nginx -v
nginx -V 2>&1 | grep -o -- '--with-http_v2_module'
The first command shows the version. Everything from 1.9.5 to 1.31.8 contains the vulnerable code. The second checks whether the HTTP/2 module is built in: if there is no output, CVE-2026-123007 does not apply to you (but the other four remain, depending on the configuration).
⚠️ The package version doesn't always tell the truth. Distributions often backport fixes into old versions without changing the number in nginx -v. So for packages from OS repositories, look at the package changelog (section 3), not just the version number.
2.2 Whether HTTP/2 Is Enabled in the Configuration
sudo nginx -T 2>&1 | sed 's/#.*//' | grep -nE 'listen[[:space:]].*(http2|quic)|^[[:space:]]*(http2|http3)[[:space:]]+on[[:space:]]*;'
The command prints all listen ... http2 lines, listen ... quic lines, and the http2 on; / http3 on; directives. If there are matching lines, the corresponding protocol is enabled. Note that nginx -T reads files on disk, while the running process may have started with an older configuration.
2.3 Whether HTTP/2 Is Reachable From Outside
openssl s_client -connect example.com:443 -servername example.com -alpn h2 < /dev/null 2>&1 | grep -i "ALPN"
The line ALPN protocol: h2 means the server accepts HTTP/2. Run the check from another network and, if a CDN or load balancer sits in front of nginx, also query your server's IP directly.
2.4 Other Dangerous Components
sudo nginx -T 2>&1 | grep -nE 'mirror|resolver|auth_http|quic|http3'
Found mirror or resolver? Check whether the address in proxy_pass is built from request data. Found auth_http? You have a mail proxy.
3. How to Update
3.1 Fixed Versions
- nginx 1.31.9 (mainline) fixes all five vulnerabilities.
- nginx 1.30.7 (stable): the fixed release of the stable branch.
- NGINX Plus: fixed builds 37.0.8.1 and 37.3.0.1.
Older branches did not receive fixes: if you are on them, you need to move to a supported branch.
3.2 Distribution Packages: Check the Changelog
As of November 18, 2026, fixes for Ubuntu were already being prepared, while for Debian 12/13 and RHEL 8/9/10 there were no ready packages yet. The situation changes within hours, so check your distribution's security tracker directly.
# Debian / Ubuntu
sudo apt update
sudo apt install --only-upgrade nginx
apt changelog nginx | grep -m3 CVE-2026-123007
# AlmaLinux / Rocky / RHEL
sudo dnf upgrade nginx
rpm -q --changelog nginx | grep -m3 CVE-2026-123007
If the changelog mentions CVE-2026-123007, the fix is in the package, even when the version number looks old. If it doesn't, the package is not fixed yet: move on to the temporary measures (section 4) or install nginx from the official nginx.org repository.
3.3 Docker
docker pull nginx:stable
docker run --rm nginx:stable nginx -v
docker compose up -d --force-recreate
First make sure the image already contains the fixed version (1.30.7 or newer for stable). Images built earlier don't update themselves: they need to be rebuilt and the containers recreated. For Docker Swarm, update the image in the service (docker service update --image ...), and a rolling update will roll it out across the nodes.
3.4 Be Sure to Restart, Not Reload
sudo nginx -t
sudo systemctl restart nginx
After a package update, the running process keeps using the old binary, and reload keeps the old worker processes and long HTTP/2 sessions alive. Only restart guarantees that the fixed version is running. After that, run nginx -v and the check from section 2 again.
4. Temporary Measures While There Is No Package
4.1 Disable HTTP/2 (Closes CVE-2026-123007 and CVE-2026-123633)
# nginx 1.25.1 and newer: in every server block with HTTPS
server {
listen 443 ssl;
http2 off;
...
}
# older versions: remove http2 from listen
# was: listen 443 ssl http2;
# now: listen 443 ssl;
Check all server blocks that share one address and port. Clients will switch to HTTP/1.1 and will barely notice, but native gRPC will stop working.
4.2 Disable HTTP/3 (CVE-2026-121810)
Remove the listen ... quic directives, set http3 off;, and clear the header: add_header Alt-Svc 'clear' always;. Optionally, block UDP 443 on the firewall.
4.3 Mirroring and DNS (CVE-2026-123634)
Disable mirror if you don't need it, and instead of a request-dependent address in proxy_pass, specify a fixed upstream group. The mirror_request_body on mode only stops the test exploit but doesn't eliminate the bug, so it can't be relied on.
4.4 Mail Proxy (CVE-2026-113425)
Bind the IMAP/POP3/SMTP listeners to loopback or restrict access with an allowlist of addresses on the firewall. This is the only temporary measure for this vulnerability.
4.5 The Kernel Chain: SCTP
If you don't need SCTP (and on ordinary web servers it is almost never needed), prohibit loading the module:
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
This blocks loading via modprobe, but it doesn't unload an already loaded module and doesn't help if SCTP is built into the kernel. To check whether it is loaded: lsmod | grep sctp. A kernel fix was not yet available at the time of publication, so watch for kernel updates from your distribution.
⚠️ Temporary measures are not a substitute for updating. Disabling HTTP/2 does not close CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425. It is only a way to buy time, not a final solution.
5. Is It Already Being Exploited, and How to Keep the Situation Under Control
As of November 18, no attacks "in the wild" had been reported, and CVE-2026-123007 was not in the CISA catalog of known exploited vulnerabilities. There is a public proof-of-concept, but with significant limitations: it is designed for a fresh container with a clean heap, is unlikely to work on a busy server, and requires a huge volume of HTTP/2 traffic in a single connection. The researchers claim that their own exploit worked even under concurrent load, but they have not published the code.
This is no reason to postpone updating. Public PoCs usually improve quickly, and critical nginx vulnerabilities with an open port become a target for automated scanners very fast.
What to Do After Updating
- Make sure
nginx -vshows the fixed version (or the package changelog contains the CVE) and that the process has been restarted:ps -o lstart= -C nginxwill show when it started. - Review the nginx logs for the past few days: unusually large HTTP/2 connections and crashes of worker processes (
worker process ... exited on signal 11) inerror.log. - For critical servers, check for unusual processes and new files in system directories.
- Run nginx as non-root, restrict the container (
read_only,cap_drop: ALL), and where possible keep a proxy or CDN that terminates HTTP/2 in front of the server.
Conclusion
NGINX2Root is five critical vulnerabilities, the main one of which affects all nginx versions with HTTP/2 enabled from 1.9.5 to 1.31.8. The course of action is simple: check the version and configuration (section 2), update the package or image to a fixed version (1.30.7 for stable or 1.31.9), restart nginx, and confirm the result. If there is no package yet, disable HTTP/2 and HTTP/3, and on hosts with no need for SCTP, prohibit its module. All of this takes a few minutes, while the price of delay can be root access to the server.
Ansible can help automate such checks and updates across dozens of servers: we cover it in detail in the "Ansible" article series on our blog, starting with the architecture and first commands.
🛡️ Need Help With the Update?
If you aren't sure whether your server is vulnerable, or you don't want to touch production yourself, message us. We will help you check your nginx version, update the package or image, and restart the service safely.
🖥️ Dedicated Servers
- From $90/mo, full control over the hardware and the system
- No resource-sharing neighbors: predictable performance
- 24/7 support: we'll help with updates and diagnostics
💻 Cloud (VPS) Hosting
- From $19.95/mo, KVM isolation, dedicated vCPU and RAM
- Full root access: you manage software versions and the kernel yourself
- Isolation at the virtualization level: your own kernel, not one shared with neighbors
💬 Not sure which option you need?
💬 Message us, and we'll help you choose!
Frequently Asked Questions
- Does this affect me if nginx sits behind Cloudflare or another CDN?
It partially reduces the risk: the CDN terminates client HTTP/2 connections, and your nginx sees traffic from the CDN. But if the server is reachable directly by IP, it can be attacked too. So update regardless of whether you have a CDN, and restrict direct access to the server to CDN addresses only.
- How do I find out whether HTTP/2 is running on my server?
Run
openssl s_client -connect domain:443 -servername domain -alpn h2and look forALPN protocol: h2, and in the configuration use the command from section 2.2. If the HTTP/2 module is not built into the binary, CVE-2026-123007 does not apply to you.
- Why is the version in nginx -v new, but the check says I'm vulnerable (and vice versa)?
Distributions backport fixes into old versions without changing the number, so for OS packages trust the changelog (
apt changelog nginxorrpm -q --changelog nginx), not just the number. Another reason: the package was updated but the process was not restarted, and the old binary is running.
- Is it enough to disable HTTP/2?
It closes CVE-2026-123007 and CVE-2026-123633, but not CVE-2026-123634 (mirroring and DNS), CVE-2026-121810 (HTTP/3), and CVE-2026-113425 (mail proxy). It is an acceptable temporary measure while there is no package, but there is only one final solution: updating.
- Is my nginx safe in a Docker container?
No, a container does not protect against this problem. A container shares the kernel with the host, so chained with the kernel vulnerability (SCTP), the researchers obtained root on the host. Update the image, recreate the containers, and, if you don't need SCTP, prohibit its module on the host.
- Are there already attacks and public exploits?
As of November 18, no attacks had been reported. A public PoC exists with significant limitations (it needs a clean container and a very large volume of HTTP/2 traffic), and the researchers' more powerful exploit has not been published. This is no reason to delay: such a situation usually changes quickly.
- Why is a restart needed rather than a reload?
Reload starts new worker processes with the new configuration, but the old ones live until their connections finish, and long HTTP/2 sessions can live for hours. In addition, after a package update, reload does not replace the already running binary. Restart guarantees that the fixed version is what is running.