nginx2root on Ubuntu and Debian: Fixed NGINX 1.30.7 via APT
by Danila Vershinin, , revisited on
dnf, yum or apt upgrades. It maintains the largest RPM repository of NGINX module packages and Varnish VMODs, with APT packages for Debian and Ubuntu.
Free to install; commercial production use requires a subscription.
To fix nginx2root on Ubuntu or Debian, install a fixed nginx package and restart NGINX. Ubuntu shipped one on November 19 for 22.04 and newer, Debian has not yet, and Ubuntu 20.04 gets it through Ubuntu Pro only. NGINX 1.30.7 from the GetPageSpeed repository covers all of them: the commands below replace the distribution build in place on Ubuntu 20.04 to 26.04 and Debian 12 and 13.
curl -fsSLO https://extras.getpagespeed.com/release-latest.deb
sudo apt-get -y install ./release-latest.deb
sudo apt-get update
sudo apt-get -y -o Dpkg::Options::=--force-confold install nginx
sudo systemctl restart nginx
nginx -v
Free to install; commercial production use requires a subscription. Without one, a small license notice appears on HTML pages after 30 days. On a GetPageSpeed build, nginx -t prints one extra warning line about a license token and still reports that the test is successful.
Not sure whether your server is affected? Paste the output of dpkg -l nginx into the nginx2root checker. It reads the package version, so it can tell a backported fix from an old version number.
What nginx2root is
CVE-2026-123007 HTTP/2 flow control NGINX 1.9.5 to 1.31.8
CVE-2026-123633 HTTP/2 use-after-free NGINX 1.19.7 to 1.31.8
CVE-2026-121810 HTTP/3 use-after-free NGINX 1.25.0 to 1.31.8
CVE-2026-123634 resolver use-after-free NGINX 0.6.18 to 1.31.8
CVE-2026-113425 mail proxy use-after-free NGINX 0.5.33 to 1.31.8
Fixed in: NGINX 1.30.7 (stable) and 1.31.9 (mainline)
nginx2root is the name Xint gave to five memory-safety flaws in NGINX, published on November 18, 2026. The ranges above are the ones in the nginx.org security advisories.
The lead flaw, CVE-2026-123007, needs nothing but HTTP/2. An unauthenticated attacker can run commands as the NGINX worker process. Xint’s write-up then chains a separate, still unpatched Linux kernel flaw in SCTP to become root. A public proof of concept exists. There was no confirmed exploitation as of November 19, 2026.
nginx2root on Ubuntu and Debian: who has a fix
As of November 19, 2026:
| Release | Distribution package | Status |
|---|---|---|
| Ubuntu 22.04, 24.04, 26.04 | 1.18.0-6ubuntu14.23, 1.24.0-2ubuntu7.20, 1.28.3-2ubuntu1.13 | Fixed on November 19 (USN-9159-1) |
| Ubuntu 16.04, 18.04, 20.04 | 1.18.0-0ubuntu1.7+esm5 on 20.04 | Fixed for Ubuntu Pro only |
| Debian 12 and 13 | 1.22.1, 1.26.3 | “vulnerable”: no advisory |
The sources are the Ubuntu CVE tracker and the Debian security tracker.
Both distributions backport fixes. Therefore nginx -v on a fixed Ubuntu 24.04 still prints 1.24.0, and Debian’s update will keep 1.22.1 or 1.26.3. Only the full package version from dpkg -l nginx changes. On Ubuntu 22.04 and newer, sudo apt-get update && sudo apt-get upgrade followed by a restart is enough. The nginx.org repository is an alternative there too, but it has no 1.30.7 build for Ubuntu 20.04.
Ubuntu 20.04 is the release to watch. It is out of standard support, so its fixed package is available through Ubuntu Pro only. A server without Ubuntu Pro stays on the affected build for good, and the same holds for Ubuntu 18.04 and 16.04.
The GetPageSpeed repository has NGINX 1.30.7 for Ubuntu 20.04, 22.04, 24.04 and 26.04 and for Debian 12 and 13. The Ubuntu 24.04 build was published at 16:18 UTC on November 18, within the hour of the disclosure.
What the upgrade changes
We tested the commands above on Ubuntu 20.04, 22.04 and 24.04 and on Debian 12 and 13, each starting from the distribution’s own package as it was on November 18, before Ubuntu’s update.
| Release | Before | After |
|---|---|---|
| Ubuntu 20.04 | 1.18.0-0ubuntu1.7 | 1:1.30.7-27~gps1+ubuntu2004+stable |
| Ubuntu 22.04 | 1.18.0-6ubuntu14.22 | 1:1.30.7-27~gps1+ubuntu2204+stable |
| Ubuntu 24.04 | 1.24.0-2ubuntu7.19 | 1:1.30.7-27~gps1+ubuntu2404+stable |
| Debian 12 | 1.22.1-9+deb12u10 | 1:1.30.7-27~gps1+deb12+stable |
| Debian 13 | 1.26.3-3+deb13u10 | 1:1.30.7-27~gps1+deb13+stable |
In every case nginx -t passed on the existing configuration afterwards. Three things are worth knowing before you run it.
One package replaces several
The single nginx package replaces nginx-common and nginx-core. The release package pins the GetPageSpeed builds above the distribution’s, so later apt-get upgrade runs keep following them.
Distribution modules are removed
The upgrade removes the distribution’s libnginx-mod-* packages. A dynamic module only loads into the exact NGINX version it was built for, as explained in NGINX module version mismatch. Install the matching nginx-module-* packages from the same repository for the modules you use, for example:
sudo apt-get -y install nginx-module-geoip2
An edited nginx.conf needs –force-confold
If you changed /etc/nginx/nginx.conf, a plain unattended apt-get -y install nginx stops at the configuration prompt:
Configuration file '/etc/nginx/nginx.conf'
*** nginx.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package nginx (--configure):
end of file on stdin at conffile prompt
E: Sub-process /usr/bin/dpkg returned an error code (1)
The -o Dpkg::Options::=--force-confold option in the command above avoids that. It keeps your file and saves the packaged one beside it as nginx.conf.dpkg-dist. With an unmodified nginx.conf, the packaged file simply replaces the old one.
Check the running binary
The package manager replaces the file on disk. The process keeps the old binary until NGINX restarts, and nginx -v reads the file, not the process. Ask the kernel instead:
sudo ls -l /proc/$(cat /run/nginx.pid)/exe
If the line ends with (deleted), the master still runs the old binary. Restart NGINX. A plain nginx -s reload does not help, because it re-reads the configuration with the binary that is already running.
Mainline, NGINX-MOD and many servers
The fix is not limited to the stable build. The mainline suites of the GetPageSpeed repository carry NGINX 1.31.9, and NGINX-MOD is at 1.30.7 for Ubuntu 24.04. If you already run one of these builds, a normal apt-get upgrade brings the fixed version.
For a fleet, three checks per server are enough. They answer the only questions that count for nginx2root on Ubuntu and on Debian alike: which package is installed, which version it is, and whether the running master uses it.
dpkg-query -W nginx; nginx -v; readlink /proc/$(cat /run/nginx.pid)/exe
A server is done when the first two lines show 1.30.7 or newer and the last one carries no (deleted).
Reading the distribution’s own fix
Ubuntu has published its backport and Debian will follow. Three things help you read them correctly.
- The version in
nginx -vdoes not move. A fixed Ubuntu 24.04 package still says 1.24.0. - The advisory, USN-9159-1 for Ubuntu or a DSA for Debian, names the first fixed package version. Compare it with the output of
dpkg -l nginx. - A backport covers the CVEs its advisory lists. AlmaLinux, for example, closed the two HTTP/2 flaws first and the other three in a second build the same day. Therefore, check that all five CVE ids are in the advisory.
The nginx2root checker follows these advisories, so pasting the dpkg -l nginx line stays the quickest test.
Stopgaps if you cannot update yet
Each stopgap switches off the feature one flaw lives in. The vulnerable code stays in the binary, so these buy time and nothing more.
Turn HTTP/2 off
This closes CVE-2026-123007 and CVE-2026-123633. On NGINX 1.25.1 and newer, set http2 off; in every server block that shares the listening address and port. On older versions, such as the 1.18.0 of Ubuntu 22.04, remove http2 from the listen directives instead.
listen 443 ssl;
http2 off;
Then reload and check from outside:
sudo nginx -t && sudo nginx -s reload
openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>&1 | grep -E 'ALPN protocol|No ALPN'
With HTTP/2 on, the check prints ALPN protocol: h2. On NGINX 1.30.7 with http2 off; we got No ALPN negotiated. Native gRPC stops working without HTTP/2.
Close the other paths
- CVE-2026-121810: remove every
listen ... quicline and sethttp3 off;. - CVE-2026-123634: point
proxy_passat a fixed upstream group, so that no name is resolved while a request is handled. - CVE-2026-113425: keep untrusted clients away from the mail proxy listeners.
Additionally, block the kernel half. On hosts that do not use SCTP:
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
The nginx2root page has the details for each stopgap and the detection commands. For a review of your whole configuration, use the NGINX config checker.
FAQ
Is nginx -s reload enough after the update?
No. A reload keeps the running binary. Restart NGINX, then confirm with the /proc check above.
Why does nginx -v still show the old version after a distribution update?
Ubuntu and Debian backport fixes into the version they ship. Compare the full version from dpkg -l nginx with the advisory instead.
Does disabling HTTP/2 fix nginx2root?
It blocks two of the five CVEs and fixes none. The resolver, mail proxy and HTTP/3 flaws do not need HTTP/2.
Do my dynamic modules need an update too?
Yes. Every module must be built for 1.30.7. The nginx-module-* packages in the GetPageSpeed repository are rebuilt for each NGINX release and update in the same transaction.
What about RHEL, Rocky Linux, AlmaLinux and CentOS?
See nginx2root on RHEL, Rocky Linux, AlmaLinux and CentOS.
Conclusion
Today’s fix is only as good as your next update. The next NGINX advisory will leave some servers behind again, and you will not notice which ones. GetPageSpeed Amplify runs scheduled gixy scans across every host and ties findings to live NGINX runtime metrics. Drop-in compatible with the deprecated nginx-amplify-agent (EOL January 2026).
Ubuntu 22.04 and newer now have their own nginx2root backport, and Debian will follow. On Debian today, and on Ubuntu 20.04 without Ubuntu Pro, NGINX 1.30.7 from the GetPageSpeed repository closes all five CVEs with one apt-get install. Check any server with the nginx2root checker, then see the subscription plans for production use.