If NGINX sits in front of your Next.js app, Node.js service or internal API, there is a fair chance it is accepting HTTP/2 connections that nobody remembers enabling. The NGINX HTTP/2 flaw tracked as CVE-2026-123007, nicknamed "nginx2root", lets an unauthenticated attacker run code on the server under certain conditions. Fixed releases shipped on 18 November 2026, but Ubuntu's own packages have not caught up yet.
A bug that has shipped in NGINX since 2015
According to The Hacker News, the flaw has been in NGINX's open-source code since version 1.9.5, released on 22 September 2015. Every release from 1.9.5 through 1.31.8 is affected, including the October security releases. The fixes are 1.31.9 (mainline) and 1.30.7 (stable).
Ubuntu's CVE tracker describes the mechanism: while processing a particular HTTP/2 traffic pattern, the flow control window can exceed its allowed threshold, causing a heap buffer overflow. Usually the result is a crashed worker process. Code execution requires ASLR to be disabled or bypassed.
Researchers at Wiz and Xint say they bypassed ASLR and executed code in testing. The CVSS 4.0 score is 9.2 out of 10, and Ubuntu rates its priority High.
Real-world risk: no attacks seen yet, but a public PoC exists
When the source article was published, neither the vendor nor the researchers had reported attacks, and the flaw was not in CISA's KEV catalog. Proof-of-concept code, however, is already public on GitHub.
Code execution lands with the privileges of an NGINX worker, not root. Even so, Xint reported escalating to root through a separate Linux kernel SCTP bug, even when NGINX ran inside a Docker container. Do not treat the container as a sufficient barrier.
Rapid7's demonstration needed roughly 128 GB of HTTP/2 traffic, so an attacker needs a fast link and some time. That is friction, not a reason to wait.
Check whether your server speaks HTTP/2
The bug is only reachable when HTTP/2 is on. Search your configuration first:
grep -rnE "http2" /etc/nginx/A listen 443 ssl http2; line or http2 on; means that server block accepts HTTP/2. To confirm from outside:
openssl s_client -alpn h2 -connect example.com:443 </dev/null 2>/dev/null | grep "ALPN"The output ALPN protocol: h2 means the server accepts HTTP/2. If a CDN sits in front, test the NGINX origin directly: an origin that only speaks HTTP/1.1 cannot be attacked this way.
Then check the running version:
nginx -v
dpkg -l nginx | tail -n 1On distribution packages, the version string may not change even when a fix is backported. Compare the full package version against the distribution's advisory rather than relying on nginx -v alone.
No fixed Ubuntu package yet: turn HTTP/2 off while you wait
Ubuntu's CVE page currently lists nginx as Vulnerable on releases from 16.04 LTS through 26.10, including 22.04 and 24.04 LTS. The Hacker News also reports that Debian has no fixed package. If you install NGINX from the Ubuntu repositories, running apt upgrade is not enough yet.
CIRCL (Luxembourg) suggests disabling HTTP/2 as a temporary measure. On NGINX 1.25.1 and later:
server {
listen 443 ssl;
http2 off;
# ...rest of your config unchanged
}On NGINX 1.9.5 through 1.25.0, remove http2 from the listen directive: listen 443 ssl http2; becomes listen 443 ssl;. Then validate and restart:
sudo nginx -t && sudo systemctl restart nginxRerun the openssl check; no h2 line means you are done. This blocks CVE-2026-123007 and CVE-2026-123633 but not the other three flaws in this release. The trade-off is that browsers fall back to HTTP/1.1, which may slow page loads slightly.
Upgrade to 1.31.9 or 1.30.7 and restart properly
If you use the official Docker images, the source article notes that 1.31.9 and 1.30.7 tags are available, including Alpine variants. For example:
docker pull nginx:1.30.7
docker compose up -d --force-recreateFor packages from nginx.org's own repository, update and then fully restart the process or use the live binary upgrade. A plain reload leaves the old executable running and existing connections can stay on old workers.
The same releases fix four more flaws, each scoring 9.2 and each needing its own setup:
- HTTP/3 enabled (CVE-2026-121810).
- NGINX used as a mail proxy (CVE-2026-113425).
- A proxied server name built from variables combined with SSI or
mirrorsubrequests (CVE-2026-123634). - HTTP/2 with a worker running low on
worker_connectionswhile proxying to a backend (CVE-2026-123633).
Extra hardening and signs of attack
If the host does not use SCTP, block the module to cut off the privilege-escalation path Xint demonstrated:
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.confThis does not unload a module that is already loaded, and it does nothing if SCTP is built into the kernel.
CIRCL suggests watching for NGINX workers launching unexpected programs, abnormal worker exits or core dumps, long-lived HTTP/2 connections with heavy inbound traffic but few logged requests, and unusual outbound connections or DNS lookups. A clean access log does not rule out an attack, since HTTP/2 control frames normally do not appear as requests. No single sign is proof on its own.
What to do today
- List every server and container running NGINX, including reverse proxies in front of Next.js apps.
- Identify which ones have HTTP/2 or HTTP/3 enabled.
- For Ubuntu-repository installs: disable HTTP/2, watch for the USN, and update when the fixed package lands.
- For Docker: pull 1.30.7 or 1.31.9 and recreate the containers.
- Check SCTP and ASLR (
cat /proc/sys/kernel/randomize_va_spaceshould return 2).
It is also a good moment to revisit other HTTP/2 issues at different layers, such as the 16 Node.js vulnerabilities patched recently or the Next.js advisories of 2026. And if you run an image registry, the post on the Red Hat Quay flaw is a reminder that the deployment chain needs auditing too. Set aside this morning to build the inventory and decide between a temporary HTTP/2 shutdown and an immediate upgrade.
References
- The Hacker News, "10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers", 18 Nov 2026: https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html
- Ubuntu Security, CVE-2026-123007, 18 Nov 2026: https://ubuntu.com/security/CVE-2026-123007






