Hey Nginx user, if you're sipping your morning coffee while reading this, put the cup down before you burn yourself. I gotta tell you something horrifying.

On November 18, 2026, F5 disclosed five holes in Nginx. The two worst are in HTTP/2, which almost every server has on:

  1. CVE-2026-123007: an integer underflow in HTTP/2 flow control. Rated 9.2, critical. Every open-source Nginx from 1.9.5 to 1.31.8 has it. That's over ten years of releases.

  2. CVE-2026-123633: a use-after-free that shows up when Nginx proxies requests to a backend. Which is what most of us use it for.

The other three hit the DNS resolver, HTTP/3, and the mail proxy.

So what does an attacker actually get? In plain words: a stranger can read your users' passwords, change your website, and, with one more bug, take over the whole server. Reportedly, researchers wrote a working exploit in minutes with a cheap AI model. If they can, so can anyone.

But don't panic yet. Let's check whether your server is exposed (90% chance it is). On Ubuntu, run:

nginx -v
apt policy nginx

nginx -v shows you the upstream version, and apt policy gives you the exact package build: "Installed" is what you run, "Candidate" is the newest build your package sources offer. The build is what tells you whether the fix is in.

Here's what mine said:

nginx version: nginx/1.24.0 (Ubuntu)
  Installed: 1.24.0-2ubuntu7.19
  Candidate: 1.24.0-2ubuntu7.19

1.24.0 sits right in the vulnerable range. Ubuntu backports the fix without bumping the version, so a patched server says 1.24.0 too. The difference is in the package build: the fixed one is 1.24.0-2ubuntu7.20 (note the 7.20 at the end). Small difference, huge impact.

Luckily, the fix is already in Ubuntu's official repos. Here's how to apply it:

sudo apt update
sudo apt install --only-upgrade nginx

That updates Nginx and nothing else. As a side note, a plain sudo apt upgrade works too, if you're happy to update everything at once. Just know it may restart other services (Docker, for one) and pull in a new kernel that wants a reboot.

After applying the fix, check that it's in:

apt changelog nginx | grep CVE-2026-123

If you see CVE-2026-123007 and CVE-2026-123633 in there, you're patched. Now restart Nginx:

sudo systemctl restart nginx

Not on Ubuntu? Same idea: get a fixed build from your distro, or move to 1.30.7 (stable) or 1.31.9 (mainline) from upstream. If you run Nginx in Docker, that means pulling the new image and recreating the container.

Done? Now pick up that coffee. It's cold by now, but cold coffee is a much smaller problem than a stranger running code on your server.

If this saved you a headache, share it with someone who runs Nginx.