NC4-ALR-2026-000017 : Critical NGINX2Root Remote Code Execution Vulnerabilities Impacting NGINX Open Source and NGINX Plus
Introduction

The National Cyber Coordination and Command Centre (NC4) draws attention to the disclosure of five critical vulnerabilities affecting NGINX Open Source and NGINX Plus, collectively referred to as "NGINX2Root". The vulnerabilities, identified as CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425, were publicly disclosed on 18 November 2026.

 

Impact

The five vulnerabilities involve memory corruption flaws affecting various NGINX modules. Each vulnerability requires specific configuration conditions to be exploitable, with CVE-2026-123007 presenting a significant concern as it requires only HTTP/2 to be enabled on a vulnerable NGINX server.

F5 has assigned all five vulnerabilities CVSS v3.1 scores of 8.1 (High) and CVSS v4.0 scores of 9.2 (Critical).

  1. CVE-2026-123007: An integer underflow vulnerability in HTTP/2 flow-control processing that can result in heap memory corruption and unauthenticated remote code execution. Affects NGINX versions 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8. A publicly available PoC demonstrates exploitation under specific conditions, requiring approximately 128 GB of HTTP/2 traffic over a single connection, sufficient bandwidth to complete within NGINX's default one-hour connection limit, and specific x86-64 processor features. Researchers have stated that more reliable exploits that work over the internet exist but are being withheld. Fake exploits claiming to target NGINX2Root are also circulating and should not be executed.
  2. CVE-2026-123633: A use-after-free vulnerability in HTTP/2 connection handling when NGINX forwards requests to an upstream server while a worker process is short of available connections (worker_connections). Affects versions 1.19.7 through 1.31.8.
  3. CVE-2026-121810: A use-after-free vulnerability in HTTP/3 (QUIC) connection handling when forwarding requests to an upstream server. Affects versions 1.25.0 through 1.31.8.
  4. CVE-2026-123634: A use-after-free vulnerability in DNS resolver processing requiring a resolver directive, a proxy_pass destination built from request variables, and a subrequest (such as mirror with mirror_request_body off, or SSI) resolving the same hostname. Affects versions 0.6.18 through 1.31.8, subject to the vulnerable configuration.
  5. CVE-2026-113425: A use-after-free vulnerability in the NGINX mail proxy module when a client disconnects during authentication processing. Exploitation requires mail proxy configurations using proxy on and auth_http. Affects versions 0.5.33 through 1.31.8.

Privilege Escalation Chain: Successful exploitation of the NGINX vulnerabilities could allow arbitrary code execution with the privileges of the NGINX worker process. Researchers have demonstrated that CVE-2026-123007 can be chained with a separate Linux kernel vulnerability involving the Stream Control Transmission Protocol (SCTP) subsystem to obtain root-level privileges on the underlying host, including from within Docker containers. Exploitation of this additional vulnerability depends on the affected kernel and system configuration.

 

Brief Description

The vulnerabilities could allow an unauthenticated remote attacker to execute arbitrary code with the privileges of the NGINX worker process under specific configuration conditions. Security researchers have demonstrated that CVE-2026-123007 can be chained with a separate, unpatched Linux kernel vulnerability to escalate privileges to root, including escaping from a Docker container to the underlying host. F5 states that code execution requires Address Space Layout Randomisation (ASLR) to be disabled or bypassed. However, researchers have demonstrated an ASLR bypass against official NGINX builds. As of 18 November 2026, there were no confirmed reports of exploitation in the wild, and none of the vulnerabilities had been added to the CISA Known Exploited Vulnerabilities (KEV) Catalog.

 

Affected Product

Affected Versions (NGINX Open Source):

  • NGINX Open Source versions 0.5.33 through 1.30.6, depending on the vulnerability (CVE-2026-123007 affects 1.9.5 and later).
  • NGINX Open Source versions 1.31.0 through 1.31.8.
  • Branches older than 1.30 will not receive a fix and should be upgraded to 1.30.7 or 1.31.9, or updated through a vendor package containing the backported fix.

Affected Versions (NGINX Plus):

  • NGINX Plus versions 37.0.0 through 37.0.7.1.
  • NGINX Plus versions 37.1.0 through 37.2.0.1.
  • NGINX Plus R34, R35, and R36.

Other Potentially Affected Systems:

  • Third-party applications and appliances incorporating vulnerable NGINX builds.
  • Container images using affected NGINX versions.
  • Kubernetes ingress controllers and other products incorporating vulnerable NGINX components. F5 NGINX Ingress Controller 5.8.0 and NGINX Gateway Fabric 2.9.0 include the fixed NGINX 1.31.9. NGINX Plus-based images should be verified against F5's advisory. F5 lists BIG-IP, BIG-IQ and F5OS as not affected.

Fixed Versions:

  • NGINX Open Source (stable): 1.30.7
  • NGINX Open Source (mainline): 1.31.9
  • NGINX Plus: 37.0.8.1 or 37.3.0.1, depending on the release branch.

No fix is available for NGINX Plus R34, R35, or R36. Administrators should upgrade to NGINX Plus 37.0.8.1 or 37.3.0.1.

Note: Organisations using Linux distribution packages or third-party products should verify the applicable vendor security updates, as some distributions may backport security fixes without changing the upstream NGINX version number.

At the time of disclosure, fixed packages had not been released for several major distributions, including Debian, Ubuntu and Red Hat Enterprise Linux, or for OpenResty. Organisations relying on these packages should apply the temporary mitigations below until vendor updates are available.

Official NGINX Docker images have been updated. Use explicit version tags (for example, nginx:1.31.9-alpine) to ensure the fixed build is pulled.

The retired community-maintained Kubernetes Ingress NGINX project no longer receives security patches and should be migrated to a supported alternative.

 

Recommendation

Organisations operating internet-facing NGINX servers with vulnerable configurations should assess their systems for potential exploitation attempts or compromise.

The following indicators warrant further investigation:

  1. Unexpected NGINX worker process crashes, restarts, or segmentation faults (for example, error log entries such as “worker process … exited on signal 11”). These events may indicate exploitation attempts but are insufficient on their own to confirm successful compromise.
  2. Unusual processes or shell commands initiated by NGINX worker processes, particularly unexpected execution of system utilities.
  3. Sustained or unusually high inbound HTTP/2 traffic, particularly over long-lived connections with few logged requests. The HTTP/2 frames used to trigger CVE-2026-123007 are not recorded in access logs, so clean access logs do not rule out exploitation.
  4. Anomalous outbound connections or DNS lookups originating from NGINX servers.
  5. Unexpected file modifications, newly created files, or unexplained configuration changes.
  6. Unexpected loading of the SCTP kernel module (for example, visible in lsmod output or kernel logs), particularly on systems where SCTP is not normally required.
  7. Unexpected modifications to system logs or evidence of unauthorised privileged activities.

Organisations should correlate these findings with endpoint telemetry, process execution records, network traffic, and NGINX access and error logs to determine whether suspicious activity has occurred.
 

NC4 strongly recommends that network defenders and system administrators implement the following measures:

  1. Identify and Assess Affected Systems: Identify all NGINX Open Source and NGINX Plus deployments, including those embedded within third-party applications, appliances, and container images. Prioritise internet-facing systems and verify their versions and configurations.
  2. Apply Security Patches: Upgrade affected NGINX Open Source instances to versions 1.30.7 (stable) or 1.31.9 (mainline) or apply the appropriate fixed NGINX Plus release. Perform a full service restart or a live binary upgrade to ensure the patched binary is running. A configuration reload (nginx -s reload) alone leaves the old binary in use.
  3. Implement Temporary Mitigations: Where immediate patching is not possible, consider the following measures based on the affected configuration:
    • Disable HTTP/2 on affected listeners to mitigate CVE-2026-123007 and CVE-2026-123633, by removing the http2 parameter from listen directives. On version 1.25.1 and later, disable HTTP/2 by setting http2 off. Note that this may affect clients that require HTTP/2, such as gRPC. For Ingress NGINX, set use-http2: "false" in the ConfigMap.
    • Disable HTTP/3 (QUIC) on affected listeners to mitigate CVE-2026-121810, by removing quic listeners, setting http3 off, clearing the Alt-Svc header and blocking UDP on the affected port.
    • Replace variable-based proxy_pass destinations with fixed upstream configurations, and disable mirror and SSI where not required, to reduce exposure to CVE-2026-123634.
    • Restrict access to vulnerable mail proxy services configured with proxy on and auth_http to trusted networks or bind them to localhost to mitigate CVE-2026-113425.
    • Prevent loading of the Linux SCTP kernel module on systems that do not require it, where applicable (for example, by adding install sctp /bin/false to a configuration file in /etc/modprobe.d/). This does not unload an already loaded module or disable SCTP built directly into the kernel.

These measures are temporary and do not replace the need to apply security patches.

  1. Verify System Exposure: Review installed NGINX versions, enabled modules, and active configurations. Administrators may use the following commands to support verification:
  • nginx -v to identify the NGINX version.
  • nginx -V to review compiled modules and build options.
  • nginx -T to inspect active configuration settings, including HTTP/2, HTTP/3, proxy, resolver, and mail proxy configurations (for example, nginx -T | grep -nE 'http2|http3|quic|resolver|mirror|auth_http'). Where NGINX is installed from a distribution package, compare the full package version against the distribution's security advisory rather than relying on nginx -v.

Administrators should verify whether HTTP/2 or HTTP/3 is actively enabled, as the presence of a compiled module alone does not establish exposure.

  1. Strengthen Security Monitoring: Monitor NGINX error logs for abnormal worker process termination, segmentation faults, and unusual connection behaviour. Review process execution events for unexpected commands initiated by NGINX workers (for example, using an auditd execve rule for the NGINX worker user) and investigate suspicious outbound connections.
  2. Perform Backups and Validate Updates: Maintain current backups of NGINX configurations and relevant application data before deploying updates. Verify that the patched services are functioning correctly and that the intended security fixes have been applied.

Disclaimer

This advisory reflects information available to NC4 as of 19 November 2026. Exploitation activity affected product coverage and vendor remediation guidance may change as additional information becomes available. Organizations should continue to monitor official vendor and government cybersecurity advisories for updates.

References

NGINX Security Advisories    https://nginx.org/en/security_advisories.html

F5 Security Advisory – CVE-2026-123007    https://my.f5.com/manage/s/article/K000163926

F5 Security Advisory – NGINX Vulnerabilities    https://my.f5.com/manage/s/article/K000164058

Rapid7 – CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE    https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/

CERT-EU Security Advisory 2026-022 – Critical Vulnerabilities in Nginx    https://www.cert.europa.eu/publications/security-advisories/2026-022/

Xint – NGINX2Root: New Remote Code Execution Vulnerabilities in NGINX Require Urgent Patching    https://xint.io/blog/nginx2root-remote-code-execution

Kubernetes – Ingress NGINX Retirement    https://kubernetes.io/blog/2026/01/29/ingress-nginx-statement/

Advisory