8.8 Million NGINX Services Still Potentially Exposed to Critical NGINX2Root Vulnerability
8.8 Million NGINX Services Potentially Exposed to Critical NGINX2Root Vulnerability
Approximately 8.8 million NGINX services remain vulnerable to the NGINX2Root flaws, a set of five memory bugs disclosed on November 18, 2026. The most severe, CVE-2026-123007, affects versions from 1.9.5 to 1.31.8 and can allow unauthenticated remote users to run commands as a worker process. While some services have been patched or disabled HTTP/2, many remain exposed, particularly those using HTTP/3 or mail proxy configurations.
AI summary of the linked source. Not reviewed by an editor. How this works
Run NGINX?
Get an email when a new story names NGINX, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonDespite a patch being available, approximately 8.8 million NGINX services remain vulnerable to the NGINX2Root flaws, including a critical unauthenticated remote code execution vulnerability affecting a wide range of versions. The sheer scale of exposure weeks after disclosure highlights a systemic failure in patch management processes, particularly for internet-facing infrastructure. Organizations running HTTP/3 or mail proxy configurations face heightened risk as common mitigations like disabling HTTP/2 do not fully protect them. This incident underscores that critical vulnerabilities in widely deployed web servers demand immediate, prioritized patching — not passive dependency on default update cycles.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Threat intelligence
Attack campaigns reach your sector, suppliers or software before your team hears about them.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- cve: CVE-2026-113425
- cve: CVE-2026-121810
- cve: CVE-2026-123633
- cve: CVE-2026-123007
- cve: CVE-2026-123634