DEV Community

Muhammad Muzammil
Muhammad Muzammil

Posted on

Your NGINX Server Might Be Wide Open: The 10-Minute Fix

Two critical NGINX bugs went public on November 18, 2026. If HTTP/2 is on and you haven't updated, an attacker can run code on your server without logging in. I patched my own server in about 10 minutes. Here's exactly how.

What happened (30-second version)

  • CVE-2026-123007 and CVE-2026-123633, both rated 9.2 Critical.
  • The bugs are in NGINX's HTTP/2 code, so even a perfectly secure app behind NGINX can be hit.
  • One of them has been hiding in NGINX since 2015, and a public exploit already exists.
  • Discovered by Wiz Research and other teams. Full technical details: Wiz blog.

Step 1: Check (2 minutes)

dpkg -l nginx | tail -1
sudo nginx -T 2>/dev/null | grep -n http2
Enter fullscreen mode Exit fullscreen mode

The first command shows your exact package version. Don't trust nginx -v, because it hides the distro's patch number. If the second command prints an http2 line, you're exposed.

Now see if a fix is waiting:

sudo apt update
apt changelog nginx | head -40 | grep CVE-2026-123007
Enter fullscreen mode Exit fullscreen mode

If the CVE shows up, the fix is ready to install.

Step 2: Patch (5 minutes)

sudo apt install --only-upgrade nginx nginx-common
sudo nginx -t && sudo systemctl restart nginx
Enter fullscreen mode Exit fullscreen mode

Use restart, not reload, so the new code actually runs. On RHEL use sudo dnf update nginx. On Docker, run docker pull nginx:stable and recreate the container.

Step 3: Confirm (1 minute)

dpkg -l nginx nginx-common | tail -2
systemctl status nginx --no-pager | head -3
Enter fullscreen mode Exit fullscreen mode

Both packages should show the new version (mine was 1.28.3-2ubuntu1.13), and the start time should be after the upgrade. Done.

Got a "404 Not Found" error?

That just means Ubuntu's mirrors haven't caught up yet, and nothing on your server broke. Run sudo apt update, wait a little, and retry. Meanwhile, switch off HTTP/2: remove http2 from your listen lines, add http2 off;, and reload NGINX.

That's it

Check, patch, confirm: 10 minutes, and your server is safe. Now do the same on your other servers, and share this with anyone who runs NGINX.

Source: Wiz Research, Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007, November 18, 2026.

Top comments (0)