Jessica Entwistle
November 19 2026
Five critical vulnerabilities have been identified in NGINX, the open-source web server and reverse proxy software used by an estimated 225 million websites globally. Infosecurity Magazine and The Hacker News both report that the most significant flaw, CVE-2026-123007 — nicknamed "nginx2root" — has been present in NGINX's codebase since version 1.9.5, released in September 2015. The vulnerability affects NGINX's HTTP/2 implementation and allows an unauthenticated attacker to remotely execute code on affected servers. F5, the company that maintains NGINX, released patched versions 1.31.9 and 1.30.7 on 19 November 2026.
NGINX is one of the most widely deployed web server technologies in the world, used extensively across UK businesses, cloud-hosted environments, managed hosting platforms, and enterprise infrastructure. Because the flaw requires no authentication to exploit, any internet-facing server running a vulnerable version of NGINX with HTTP/2 enabled is potentially at risk from an external attacker. The severity of remote code execution vulnerabilities means that successful exploitation could lead to full server compromise, data exfiltration, or the deployment of further malicious tooling. The decade-long presence of this flaw in the codebase is also a broader reminder of the challenges inherent in open-source software security — widely trusted code is not always widely audited, and vulnerabilities can persist for years before being discovered. For organisations in sectors such as retail, financial services, healthcare, and professional services, where web-facing applications handle sensitive customer data, the risk profile here is meaningful and warrants prompt attention.
Organisations should begin by establishing which versions of NGINX are running across their web estate, including any instances managed through hosting providers, cloud platforms, or managed service partners. Where NGINX is self-managed, patching to version 1.31.9 (mainline) or 1.30.7 (stable) should be prioritised. Where NGINX is managed by a third party, organisations should request explicit confirmation of the patching timeline rather than assuming it has been handled. It is also worth reviewing whether HTTP/2 is enabled on any NGINX instances where it is not actively required, as disabling it on non-essential services reduces the attack surface while patching is completed. This incident is also a useful prompt to review the broader process for tracking and patching open-source components across your infrastructure.
Source: Infosecurity Magazine