Critical NGINX vulnerabilities: Our systems are already patched

F5 has fixed vulnerabilities in NGINX Open Source and NGINX Plus. ayedo has already updated the affected systems.

On November 18, 2026, F5 released security updates for several vulnerabilities in NGINX Open Source and NGINX Plus. Under certain conditions, the vulnerabilities can lead to denial of service or remote code execution. We have already updated the affected systems in our infrastructure and implemented the required security measures.

What is NGINX and why does it matter?

NGINX (pronounced “Engine X”) is widely used open-source software that serves primarily as a web server, reverse proxy, and load balancer. It is a core component of modern web infrastructure and helps keep websites, web applications, and APIs available.

As a web server, NGINX serves web pages and static content. As a reverse proxy, it accepts incoming requests and forwards them to the appropriate backend systems. As a load balancer, it distributes requests across multiple servers to improve application availability and performance.

NGINX is used by small websites as well as large enterprise and cloud environments.

Its position makes security vulnerabilities particularly relevant. NGINX often processes requests directly from the internet. Attackers may be able to exploit flaws in how it handles these requests without first obtaining credentials.

Several critical vulnerabilities disclosed

On November 18, 2026, security updates were released for several vulnerabilities in NGINX Open Source and NGINX Plus.

The issues affect several parts of the software, including HTTP/2 and HTTP/3 connection handling, proxy features, DNS resolution, mail proxy configurations, and TLS 1.3.

Several of the vulnerabilities can be exploited remotely without prior authentication. The impact depends on the version, enabled features, and configuration.

Denial of service (DoS). Under certain conditions, an attacker can crash or stall NGINX worker processes. This can disrupt access to websites and applications.

Remote code execution (RCE). According to F5, several memory safety issues can allow code to run with the privileges of the NGINX worker process under certain conditions. This risk applies when Address Space Layout Randomization (ASLR) is disabled or can be bypassed.

Vulnerabilities to check

CVE-2026-123007 – Critical HTTP/2 vulnerability

This vulnerability affects HTTP/2 connection handling. F5 rates it 9.2 under CVSS v4.0 and 8.1 under CVSS v3.1.

A flaw in HTTP/2 flow control can cause a heap buffer overflow, which can crash an NGINX worker process or corrupt its memory.

The vulnerability can be reachable remotely without authentication. A public proof of concept demonstrates that the issue can be exploited.

CVE-2026-123633 – Use after free in HTTP/2 proxy connections

This issue affects NGINX configurations that accept HTTP/2 connections and forward requests to backend systems.

Under certain conditions, closing an active HTTP/2 connection can cause NGINX to access memory it has already freed.

This type of error is called a use-after-free. It can crash a process and, in certain circumstances, allow code execution.

CVE-2026-121810 – HTTP/3 and QUIC vulnerability

This vulnerability affects HTTP/3 connection handling.

Under certain conditions, ending a QUIC connection while communicating with an upstream system can cause a use-after-free error.

The issue is relevant to systems with HTTP/3 or QUIC enabled.

CVE-2026-123634 – DNS resolver and proxy vulnerability

This issue affects the NGINX DNS resolver in certain proxy configurations. According to F5, name resolution used with Server Side Includes (SSI) or the mirror feature can lead to a use-after-free error.

DNS resolution and proxy features are common in web infrastructure. Operators should check whether their specific configuration is affected.

CVE-2026-113425 – Mail proxy vulnerability

This issue affects NGINX deployments configured as mail proxies.

A use-after-free error can occur during an authentication request under certain conditions.

The issue is primarily relevant to operators who use the affected mail proxy features.

CVE-2026-118899 – TLS 1.3 denial of service

F5’s security notification also lists a flaw that affects HTTP request handling over TLS 1.3. Affected NGINX workers can get stuck in an infinite loop and stop processing connections.

Which NGINX versions are affected?

Affected versions vary by vulnerability and NGINX edition.

Affected releases include NGINX Open Source 1.30.0 through 1.30.6 and mainline releases 1.31.0 through 1.31.8. Some vulnerabilities also affect older releases.

The fixes for NGINX Open Source were released in:

  • NGINX 1.30.7 for the stable branch
  • NGINX 1.31.9 for the mainline branch

Security updates are also available for NGINX Plus. See the individual F5 security advisories for affected and fixed releases. The NGINX security advisories list the version ranges for Open Source.

Assess exposure based on the installed version, configuration, and modules in use.

What should operators do now?

Install the applicable security updates promptly.

First, check the installed NGINX version and which affected features are enabled. Review HTTP/2, HTTP/3, TLS 1.3, reverse proxy features, and mail proxy configurations.

Then install the updates for your deployment.

After updating, verify that the running NGINX processes are using the updated software. A controlled service restart is a reliable way to load the updated binary.

If you cannot update immediately, temporary mitigations can reduce exposure to individual vulnerabilities.

For example, disabling HTTP/2 can help mitigate the HTTP/2 issues. The security updates are still needed to protect the other affected components.

Our infrastructure has already been updated

We reviewed the published advisories, identified our affected systems, and applied the required updates.

Our affected NGINX systems are up to date with respect to these published vulnerabilities.

For our customers, the required remediation on our side is complete.

Security updates are part of our day-to-day infrastructure operations. We continuously assess new vulnerabilities, review our systems, and install security updates promptly.

For core infrastructure components such as NGINX, resolving known vulnerabilities quickly is especially important.

Keeping software up to date is a basic security requirement

These NGINX vulnerabilities show why consistent patch management matters.

Even widely used, established open-source software can have serious security flaws. What matters is how quickly vulnerabilities are found, fixes are released, and operators install the available updates.

Releasing security updates is part of maintaining software. Operators are responsible for applying those updates to their deployments.

We have already updated our affected systems.

Secure infrastructure requires ongoing maintenance, monitoring, and regular updates.