nginx2root on Ubuntu: how I checked and mitigated it without upgrading nginx
The nginx2root bugs went public on 18 November 2026. Like most people I thought "fine, I'll just upgrade nginx." Then I looked at my server. It runs Ubuntu's packaged nginx, and on Ubuntu "just upgrade" wasn't an option yet. This post covers what I did instead on 20 November. I checked whether I was exposed, turned off the vulnerable features, nearly panicked over a Cloudflare false alarm, and…
The nginx2root bugs were discovered on November 18, 2026. They affect five memory-corruption bugs in nginx, including four use-after-free bugs and one integer overflow. An unauthenticated attacker could crash a worker or, in some cases, execute code as the worker. The first affected release is CVE-2026-123007, which needs only HTTP/2 to be enabled.
Most servers running Ubuntu's packaged nginx would be vulnerable since upgrading wasn't an option. The mitigation process involved checking the installed package revisions, enabling/disabling HTTP/2, and verifying the configuration. The final step was to ensure that visitors still accessed HTTP/2 despite the origin only speaking HTTP/1.1.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.