The 10-Year-Old NGINX Flaw That Could Let Anyone Run Code on Your Server

·
Listen to this article~4 min
The 10-Year-Old NGINX Flaw That Could Let Anyone Run Code on Your Server

A decade-old flaw in NGINX's HTTP/2 support allows unauthenticated attackers to execute code remotely. Fixed versions are out, but many servers may still be vulnerable. Here's what you need to know.

A decade-old bug in NGINX's HTTP/2 support is making waves, and if you're running a server with HTTP/2 enabled, you'll want to pay attention. The flaw, tracked as CVE-2026-123007 and nicknamed "nginx2root," allows an unauthenticated attacker to execute code remotely. That's right—no login required. It's been sitting quietly in the open-source code since version 1.9.5, which came out on September 22, 2015. That's over ten years of potential exposure. F5, the company behind NGINX, has released fixed versions 1.31.9 and 1.30.7 today. But the question is: how many servers out there are still vulnerable? If you're running an older version, you might be at risk. ### What Exactly Is the NGINX HTTP/2 Flaw? NGINX is a popular web server and reverse proxy that powers a huge chunk of the internet. HTTP/2 is the newer protocol that speeds up web traffic. The vulnerability lies in how NGINX handles certain HTTP/2 requests. An attacker can send a specially crafted request that triggers a buffer overflow, leading to remote code execution. The worst part? It's unauthenticated, meaning anyone with network access can exploit it. "This is about as bad as it gets for a web server vulnerability," says Michael Miller, Lead Antidetect Browser Strategist & Architect. "It's a perfect storm: a widely used server, a protocol that's enabled by default in many setups, and a flaw that's been lurking for a decade." ### Who's at Risk? If you're running NGINX with HTTP/2 enabled and haven't updated to the latest version, you're in the crosshairs. That includes: - Web hosting providers - Cloud infrastructure - Enterprises with public-facing web servers - Even home labs and small businesses The flaw affects versions from 1.9.5 up to, but not including, the fixed versions. So if you're on 1.31.8 or earlier, you need to patch ASAP. ### What Should You Do Right Now? First, check your NGINX version. You can do this by running `nginx -v` in your terminal. If you're on a vulnerable version, upgrade to 1.31.9 or 1.30.7 immediately. If you can't upgrade right away, consider disabling HTTP/2 temporarily as a mitigation. F5 has published a security advisory with more details, but the key takeaway is simple: patch now. Don't wait. This isn't a theoretical threat; it's a real exploit that's been in the wild for years without anyone noticing. ### The Bigger Picture This incident is a reminder that even mature, widely-used software can harbor critical bugs for years. It's also a wake-up call for anyone who thinks "it's been fine so far, why worry?" The answer is: because attackers only need one opening. So, take a few minutes today to check your servers. Update NGINX. And maybe set up a regular patch schedule if you haven't already. Your future self will thank you.