Protecting Websites from the nginx2root Security Flaw
November 18, 2026
Today, security researchers at Xint announced five serious flaws in nginx, the web server used by millions of sites. The collection has been named nginx2root. Its widest-reaching flaw allows a remote visitor to run code on a server whenever HTTP/2 is enabled. No account or password is required.
Fixed versions of nginx are available directly from nginx.org. Firefly's server infrastructure uses the Ubuntu ecosystem, whose nginx package has yet to receive this update. We have disabled HTTP/2 on our server while an updated Ubuntu package is being prepared. The following notes explain the risk and the change.
How the Flaw Works
HTTP/2 permits a browser to request many files through one connection. This makes modern sites faster, especially those made up of many images, style sheets, and scripts. nginx keeps track of the amount of data passing through each connection. In affected versions, a visitor can manipulate that accounting and cause nginx to write outside its allotted memory. A successful attack can give the visitor control of the nginx process.
The principal flaw, CVE-2026-123007, affects nginx versions 1.9.5 through 1.31.8. Any public nginx listener with HTTP/2 enabled is exposed. A second flaw, CVE-2026-123633, also uses HTTP/2 and affects servers that forward requests to another service. Three additional flaws concern HTTP/3, certain dynamic proxy configurations, and the nginx mail proxy.
Xint also demonstrated a separate Linux kernel flaw involving SCTP, a network protocol rarely used on ordinary web servers. Chaining the two problems allowed the researchers to gain full control of a host, including one running nginx in a container. A public demonstration for the nginx flaw appeared on the day of disclosure, which makes prompt action prudent.
A Similar Apache Problem Last Week
This announcement follows a related vulnerability in Apache HTTP Server. On November 11, Apache released version 2.4.71 to fix CVE-2026-119618, a race condition in its HTTP/2 module. The flaw affects Apache 2.4.55 through 2.4.70 and can also permit remote code execution. The Cyber Security Agency of Singapore has reported active exploitation.
Apache administrators who are awaiting an update can remove h2 and h2c from the server's Protocols setting. nginx administrators can take the equivalent precaution by disabling HTTP/2. In either case, browsers automatically use HTTP/1.1. Sites continue to operate, with a modest loss of efficiency while the temporary setting remains in place.
Disabling HTTP/2 on Ubuntu
On Ubuntu's nginx 1.24 package, HTTP/2 is commonly enabled on the secure listener:
listen 443 ssl http2;
Remove the final http2 parameter from every public TLS server block:
listen 443 ssl;
nginx 1.25.1 and later also accepts a separate directive:
listen 443 ssl;
http2 off;
After changing the configuration, test it and restart nginx. Restarting closes the old worker processes, some of which may retain established HTTP/2 connections after a reload.
sudo nginx -t
sudo systemctl restart nginx
The public site can then be checked with curl:
curl -sI -o /dev/null -w '%{http_version}\n' https://www.firefly.us/
The command should print 1.1. Native gRPC services require HTTP/2 and should be reviewed separately before making this change.
Checking the Remaining Risks
Disabling HTTP/2 addresses CVE-2026-123007 and CVE-2026-123633. Administrators should also check for HTTP/3 listeners using quic, dynamic proxy_pass settings that use a resolver, and mail proxy blocks using auth_http. The firefly.us configuration uses none of these features.
Servers that have no use for SCTP can prevent its kernel module from loading:
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
An already-loaded module remains active until the server is rebooted. The following command shows whether it is currently loaded:
lsmod | grep '^sctp'
Installing a Fixed Version
nginx 1.30.7 (stable) and 1.31.9 (mainline) contain the security fixes. The official nginx.org repository provides version 1.30.7 for Ubuntu 22.04, 24.04, and 26.04. Administrators may use those packages after checking compatibility with their server management tools and PHP configuration.
Ubuntu will probably backport the repair into its existing nginx package. When that happens, the nginx version may continue to begin with 1.24. Ubuntu package versions should therefore be checked against the Ubuntu CVE tracker.
Once a fixed package is installed and nginx has been restarted, HTTP/2 can be enabled again. Until then, serving a site over HTTP/1.1 is a small and sensible price for closing a serious opening.
Further information is available in Xint's mitigation guide, the CERT-EU advisory, and Wiz's technical analysis.