Overview
Several critical vulnerabilities have been disclosed in the widely used web server software NGINX. Both the free Open Source version and the commercial NGINX Plus edition are affected. On November 18, 2026, vendor F5 released a security update that closes a total of ten vulnerabilities – five of them at the highest severity level. NGINX is the most widely used web server in the world, so the impact is broad.
The Vulnerabilities
Five vulnerabilities are rated critical at 9.2 out of 10 points per CVSS 4.0 (8.1 on the older CVSS 3.1 scale):
CVE-2026-123007 – A flaw in HTTP/2 flow control. An attacker can trigger a heap overflow and, in the worst case, execute code on the server. Servers that only serve static files are affected as well – no backend or additional modules are required.
CVE-2026-123633 – Use-after-free (access to memory that has already been released) in HTTP/2 processing when NGINX acts as a proxy, forwards requests to an upstream server, and free connection slots run low.
CVE-2026-121810 – Use-after-free in HTTP/3 processing, also when forwarding requests to an upstream server.
CVE-2026-123634 – Use-after-free in the DNS resolver when the upstream name comes from the request (for example proxy_pass with a variable plus resolver) and mirror or SSI additionally trigger subrequests.
CVE-2026-113425 – Use-after-free in mail proxy operation when NGINX runs as a mail proxy with auth_http.
The F5 security advisories for the five vulnerabilities are linked in the advisory overview on nginx.org.
All five can be exploited remotely without authentication. In every case, an attacker can crash the worker process and corrupt memory, and in the worst case execute code with the privileges of the NGINX worker process. The remaining five vulnerabilities in the same update (severity 6.3 to 8.7) cover denial of service, a NULL pointer issue, and a client certificate bypass, among others.
Why This Is So Dangerous
Every NGINX installation with HTTP/2 enabled is affected – and that is the norm in modern TLS setups. The vulnerable code has been in the product since September 2015 (NGINX 1.9.5, which introduced HTTP/2) and is therefore present in every official version from 1.9.5 to 1.31.8. For almost eleven years, the same code has shipped millions of times worldwide.
Austria's Federal Office for Cyber Security explicitly points out in its warning that the time between a vulnerability becoming public and being exploited is getting shorter. And because NGINX sits in front of several applications as the central entry point at most customers, a single unpatched server is enough to put multiple services at risk.
Affected Versions
In short: practically all common installations are affected – from the version that Linux distributions have shipped for years to current releases.
Product | Affected Versions | Fixed Versions |
|---|
NGINX Open Source, mainline | 1.31.0 to 1.31.8 (all five vulnerabilities) | 1.31.9 |
NGINX Open Source, stable | 1.30.0 to 1.30.6 | 1.30.7 |
NGINX Open Source, older releases | from 0.5.33, 0.6.18, 1.9.5, 1.19.7 or 1.25.0, depending on the vulnerability | no fix, upgrade to 1.30.7 / 1.31.9 |
NGINX Plus 37.x | 37.0.0 to 37.0.7.1 or 37.1.0 to 37.2.0.1 | 37.0.8.1 or 37.3.0.1 |
NGINX Plus R33 to R36 | R33 to R36, varying slightly by vulnerability | no fix, upgrade to 37.3.0.1 |
What To Do Now
Affected systems should be updated to a current NGINX version immediately: Open Source to 1.31.9 (mainline) or 1.30.7 (stable), NGINX Plus to 37.3.0.1 or 37.0.8.1. The older NGINX Plus branches R33 to R36 have no fix – an upgrade is the only path.
Important: after the update, NGINX must be restarted (or a live binary upgrade performed). Reloading the configuration alone is not enough, because it does not replace the running binary.
If an update is not possible at short notice, HTTP/2 can be disabled in the affected server blocks. That blocks the two vulnerabilities CVE-2026-123007 and CVE-2026-123633, but it does not help against the other three – it is a stopgap, not a fix. Existing connections continue to run on the old workers after a reload; a full restart ends them.
One practical note: the version number alone does not always tell whether a system is already protected, because some Linux distributions backport security fixes without changing the NGINX version number. In that case only the package version changes. When in doubt, check the security advisories of the respective distribution.
How lywand Helps
Lywand identifies these vulnerabilities through our External Checks and Network Checks with immediate effect. Identification via Agent Check follows from November 20, 2026. This shows you quickly whether and where affected NGINX installations are reachable at your customers and whether action is required.
Check Customer Infrastructure Now
Act now and use the lywand checks to identify potentially affected systems and remediate vulnerabilities.
Questions or need support? Contact our Sales team at [email protected] or book a meeting.