Overview
This advisory concerns significant security vulnerabilities identified in NGINX, software widely used to support websites and online services. As NGINX is deployed across many organisations, including within services managed by third-party providers, the vulnerabilities may be relevant to businesses that are not aware they rely on it.
Business owners, senior managers and Board Members should ensure it is brought promptly to their internal IT team or external IT provider to establish whether the organisation is affected and what action is required. Public exploit code is available, increasing the urgency. Any identified exposure should be addressed without delay.
Detail
NGINX is commonly used as a web server and reverse proxy to deliver websites, route internet traffic, improve performance and help maintain service availability. It may be operated directly by an organisation or form part of cloud services, customer portals, online booking and payment systems, remote-access services, containers, appliances and products managed by an external IT provider. An organisation may therefore rely on NGINX without being aware of the underlying technology.
In simple terms, malicious internet traffic could cause a vulnerable NGINX system to fail or behave in an unintended way. In the most serious circumstances, an attacker could gain control of an affected system or access information.
The most significant issue, CVE-2026-123007, is a memory corruption vulnerability affecting HTTP/2 processing. An unauthenticated attacker could send specially crafted requests to a vulnerable server, potentially causing service disruption or memory corruption, or enabling Remote Code Execution (RCE) with the privileges of the NGINX worker process. Successful exploitation could result in system compromise, unauthorised access to data, or further attacks against connected services.
CVE-2026-123007 affects NGINX versions 1.9.5 through 1.31.8 where HTTP/2 is enabled. The vulnerability has been addressed in versions 1.30.7 and 1.31.9.
Several additional vulnerabilities were disclosed at the same time, including flaws affecting HTTP/2, HTTP/3, DNS resolver processing and NGINX mail proxy functionality. These include CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425. Under the required configurations, these vulnerabilities may also allow an unauthenticated attacker to execute code with the privileges of the NGINX worker process.
Recommended Actions
Organisations using NGINX should:
- Identify all NGINX deployments, including internet-facing web servers, reverse proxies, containers and NGINX instances embedded within other products.
- Update NGINX as soon as possible. NGINX Open Source administrators should upgrade to 1.30.7 or 1.31.9, or later.
- Prioritise internet-facing systems, particularly those with HTTP/2 or HTTP/3 enabled.
- Where immediate patching is not possible, consider temporarily disabling HTTP/2 and HTTP/3 where operationally appropriate. This can mitigate the vulnerabilities affecting those protocols, but does not address all vulnerabilities disclosed and should not be considered a replacement for patching.
- Check products that embed NGINX, such as Kubernetes ingress controllers and other appliances, and confirm their patch status directly with the relevant vendor.
Organisations should not rely solely on the version number reported by their operating system package, as Linux distributions may backport security fixes without changing the underlying NGINX version number. Check the security advisory provided by your distribution or vendor.
References