• nginx
  • Security
  • Vulnerability

Critical Memory Vulnerabilities Discovered in NGINX Plus and NGINX Open Source

Five critical vulnerabilities have been disclosed in NGINX Plus and NGINX Open Source that could allow attackers to crash your web server, corrupt memory

Five critical vulnerabilities have been disclosed in NGINX Plus and NGINX Open Source that could allow attackers to crash your web server, corrupt memory, or potentially execute malicious code. All five flaws carry a CVSS severity score of 9.2 and affect multiple versions of both products. No fixes are available yet.

CVE-2026-113425 (Mail proxy configuration)

When NGINX Plus or NGINX Open Source is configured as a mail proxy, specially crafted traffic can trigger a use-after-free vulnerability in the worker process.

A remote attacker who does not need to authenticate can exploit this flaw to crash the NGINX worker process or corrupt its memory, disrupting your service. If Address Space Layout Randomization (ASLR) is disabled on your system, or if an attacker can bypass ASLR, remote code execution becomes possible. The sources note this is a data plane issue only, with no control plane exposure.

CVE-2026-121810 (HTTP/3 configuration)

NGINX configurations that use HTTP/3 are vulnerable to a use-after-free condition that can be triggered by a remote, unauthenticated attacker.

Successful exploitation can cause the NGINX worker process to restart, resulting in a denial-of-service condition. The sources state that exploitation also depends on conditions beyond the attacker's control. As with CVE-2026-113425, code execution is possible on systems without ASLR or when ASLR can be bypassed.

CVE-2026-123007 (HTTP/2 flow control)

When NGINX processes certain traffic in HTTP/2 configurations, the flow control window can exceed its allowed threshold. This can result in a heap buffer overflow, typically followed by a segmentation fault that crashes the NGINX worker process.

An attacker could crash the worker process, corrupt memory, or potentially execute code remotely. Systems with ASLR disabled or where ASLR can be bypassed are at higher risk for code execution.

CVE-2026-123633 (HTTP/2 proxy with low connections)

This vulnerability affects NGINX configurations that use HTTP/2 for client connections and proxy those requests to a backend server. When the worker process is running low on available worker_connections, a specially crafted request can trigger a use-after-free condition.

Attackers can exploit this to cause denial-of-service or potentially execute code on vulnerable systems.

CVE-2026-123634 (Proxy with variable server names)

This flaw occurs under specific configuration conditions: NGINX must be configured as a proxy, the proxied server name must include variables, and a Server Side Includes (SSI) or mirror directive must send a subrequest to a location that resolves the same server name.

When these conditions are met, a specially crafted HTTP request can cause a use-after-free condition in the worker process. An attacker could crash the process, corrupt memory, or perform remote code execution if ASLR protections are absent or can be bypassed.

Who is affected

All five vulnerabilities affect both NGINX Plus and NGINX Open Source across multiple version ranges:

CVE-2026-113425 (mail proxy):

• NGINX Plus: versions 37.1.0 through 37.3.0.1, 37.0.0 through 37.0.8.1, and R33

• NGINX Open Source: versions 1.31.0 through 1.31.9, 1.30.0 through 1.30.7, and 0.5.33

CVE-2026-121810 (HTTP/3):

• NGINX Plus: versions 37.1.0 through 37.3.0.1, 37.0.0 through 37.0.8.1, and R33

• NGINX Open Source: versions 1.31.0 through 1.31.9, 1.30.0 through 1.30.7, and 1.25.09

CVE-2026-123007 (HTTP/2 flow control):

• NGINX Plus: versions 37.1.0 through 37.3.0.1, 37.0.0 through 37.0.8.1, and R33

• NGINX Open Source: versions 1.31.0 through 1.31.9, 1.30.0 through 1.30.7, and 1.9.5

CVE-2026-123633 (HTTP/2 proxy low connections):

• NGINX Plus: versions 37.1.0.1 through 37.2.0.1, 37.0.0.1 through 37.0.7.1, and R33

• NGINX Open Source: versions 1.31.0 through 1.31.9, 1.30.0 through 1.30.7, and 1.19.7

CVE-2026-123634 (proxy with variables):

• NGINX Plus: versions 37.1.0 through 37.3.0.1, 37.0.0 through 37.0.8.1, and R33

• NGINX Open Source: versions 1.31.0 through 1.31.9, 1.30.0 through 1.30.7, and 0.6.18

The sources note that software versions which have reached End of Technical Support are not evaluated.

How to check whether you are affected

First, determine which version of NGINX you are running. Connect to your server via SSH and run:

Text
nginx -v

Compare your version number against the affected ranges listed above.

Next, review your NGINX configuration files (typically located in /etc/nginx/nginx.conf and /etc/nginx/sites-enabled/) to determine which features you have enabled:

For CVE-2026-113425: Check if you have configured NGINX as a mail proxy. Look for mail blocks in your configuration.

For CVE-2026-121810: Check if HTTP/3 is enabled. Look for listen directives with the quic parameter or http3 directives.

For CVE-2026-123007 and CVE-2026-123633: Check if HTTP/2 is enabled. Look for listen directives with the http2 parameter.

For CVE-2026-123634: Check if you use proxy configurations with variable server names combined with SSI or mirror directives. Look for proxy_pass directives that include variables, along with ssi on or mirror directives.

If your version falls within the affected ranges and you use any of these configurations, you are vulnerable.

What to do now

No fixed versions are available yet for any of these vulnerabilities. Until patches are released, you should take the following steps:

Immediate mitigation options:

1. If you do not need the vulnerable features, disable them temporarily. For HTTP/2, remove the http2 parameter from listen directives. For HTTP/3, remove quic parameters and http3 directives. For mail proxy functionality, disable mail blocks if they are not essential.

1. Ensure Address Space Layout Randomization (ASLR) is enabled on your systems. ASLR makes it significantly harder for attackers to execute code even if they can trigger the vulnerability. On Linux systems, verify ASLR is enabled by running: cat /proc/sys/kernel/randomize_va_space (the value should be 2).

1. Monitor your NGINX error logs for unusual worker process crashes or segmentation faults. Increased crash rates may indicate exploitation attempts.

1. Implement rate limiting and request filtering at your network edge to reduce exposure to malicious traffic.

1. Review and tighten the worker_connections setting if you use HTTP/2 proxying, as CVE-2026-123633 specifically affects systems running low on available connections.

Ongoing monitoring:

Watch for security advisories from F5 Networks, the maintainer of NGINX. Subscribe to their security notification channels and check their website regularly for patch releases.

Consider implementing a Web Application Firewall (WAF) that can inspect and filter HTTP/2 and HTTP/3 traffic for anomalous patterns, though this provides only partial protection.

These vulnerabilities represent serious risks to your web infrastructure. The combination of remote exploitation without authentication and the potential for code execution makes them particularly dangerous. While waiting for patches, focus on reducing your attack surface by disabling unnecessary features and ensuring your systems have proper security hardening in place.

If you need help assessing your exposure or implementing mitigations, you can run a free security scan at https://security.azguards.com to check your website for vulnerabilities. Our team of engineers is also available to discuss your specific configuration and help you secure your NGINX deployment during this period.

Run a free scan → Talk to an engineer →

Sources

• NVD

• NVD

• NVD

• NVD

• NVD