Nginx: two critical HTTP/2 flaws expose millions of servers; here's how to check and protect yours
F5 has fixed two vulnerabilities in Nginx that allow an attacker to take control of a server without a username or password. Public proof-of-concept code is already circulating. This guide explains how to tell whether your server is at risk, which version to update to and what to do while you wait for your system's patch.
Photo: Winston Chen on Unsplash
A server that only delivered static files, with no online store, no forms and no third-party plugins, ended up executing an attacker's instructions. That is how the Wiz Research team described its exploitation of one of the two critical vulnerabilities that F5, the company responsible for Nginx, fixed on November 18, 2026. The flaws, tracked as CVE-2026-123007 and CVE-2026-123633, allow what security professionals call remote code execution: someone on the internet, without logging in, can make the machine follow their commands. The news is topping the discussion on Hacker News, and the reason is simple: Nginx powers a huge share of the web.
Nginx is a web server and also a *reverse proxy*, meaning the front door that receives incoming visits and distributes them among the applications behind it. That is why a single Nginx instance often serves several sites at once, and if that door falls, it can take all of them down with it. The two flaws share one condition: they only affect servers with HTTP/2 enabled. HTTP/2 is the modern version of the protocol that browsers and servers use to communicate, and it is enabled on a very large number of installations.
There is a striking detail for the research community. The flaws were found independently by five teams: Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint. According to Tenable, Xint detected them on October 11 and reported them to F5 on October 16. When Wiz reported the first one on October 21, F5 replied that another team had already reported it. The fact that so many groups arrived at the same weak point by different routes suggests the discovery was within reach of anyone with the necessary expertise, attackers included.
How serious it is and how many servers are exposed
Wiz and Rapid7 rate both flaws 9.2 out of 10 on the CVSS 4.0 scale, which measures vulnerability severity, placing them at the critical level. CERT-EU and OffSeq, however, list 8.1 for CVE-2026-123007, a difference that is probably explained by the use of a different version of the scale. The official score could not yet be verified. Wiz adds that ASLR, a defense that randomly relocates memory to make attacks harder, does not protect against these flaws.
Scans hint at the scale of the problem. A snapshot from Shodan, a search engine for internet-connected devices, taken by Xint on November 10 counted 56.7 million Nginx servers. Of the 11.94 million that display their version, 98.9% fall within the range affected by CVE-2026-123007. Xint cautions that seeing the version does not prove a machine is vulnerable, and that only about 21% publish it. Meanwhile, Precursor Security cites a Censys tracker showing roughly 8.8 million vulnerable services with HTTP/2 as of November 19 and less than 1% patched; another reference to the same source puts the figure at about 9.5 million. Neither figure could be verified.
As of November 19, Tenable, CERT-EU and Rescana were not reporting any real-world attacks, nor had the flaws been added to the catalog of exploited vulnerabilities maintained by CISA, the U.S. cybersecurity agency. That window may not last long: according to SOCRadar, a public proof of concept, code that demonstrates how to exploit the flaw, appeared on GitHub on the same day as the disclosure. In addition, a CIS advisory notes that another Nginx vulnerability from this year, CVE-2026-42945, went from having a public proof of concept to being exploited.
How to check your server and what to do today
The affected versions range from 1.9.5 to 1.31.8 for CVE-2026-123007, and from 1.19.7 to 1.31.8 for CVE-2026-123633. The fix is in Nginx 1.30.7, on the stable branch, and in 1.31.9, on the *mainline* branch, which receives new features first. Firms such as RedEye Security suggest two quick checks:
- Check the installed version: `nginx -v`
- Check whether HTTP/2 is enabled in the configuration the server is actually using: `nginx -T 2>/dev/null | grep -nE 'http2|http3|quic'`
If the version is within the range and HTTP/2 shows up as enabled, the priority is to update. If that is not immediately possible, the temporary measure is to disable HTTP/2. Anyone who installs Nginx from their Linux distribution should keep one nuance in mind: some distributions apply the fix without changing the version number, a practice known as *backporting*, so it is worth checking each distribution's security advisories. According to ThreatDefence, Alpine already offers the 1.30.7-r0 package. Cyber Kendra reported that Debian, SUSE and Amazon Linux had no patched package as of November 18, and Flawfence noted that Red Hat had not yet published its fix. None of these statuses has been confirmed in the vendors' own advisories.
On Kubernetes, Upwind says that F5's NGINX Ingress Controller is fixed in version 5.8.0, that the 2026-lts-r11 edition remains affected because it includes Nginx 1.31.0, and that Gateway Fabric is fixed in 2.9.0. As general warning signs, Wiz mentions unexpected crashes of Nginx worker processes and commands launched by the server itself, although it does not present them as confirmed indicators of an attack.
For Latin America, the picture is still incomplete. No country-by-country scan breakdowns were found, nor any advisories about these flaws from regional response teams, hosting panels such as cPanel or Plesk, or cloud providers, although that does not mean they do not exist. Teams at Telconet and the Escuela Politécnica Nacional in Ecuador have responded to Nginx flaws in the past. Small and medium-sized businesses, online stores and public entities that share a single server among several sites should check their version today. What to watch in the coming days are the patches from each distribution and any reports of real-world attacks.