← News

HTTP/2 Vulnerability in NGINX Allows Unauthenticated Code Execution (CVE‑2026‑123007)

A flaw in NGINX's HTTP/2 support dating back more than a decade (CVE‑2026‑123007) allows unauthenticated attackers to execute code on affected servers.

By CyberX I.T SolutionsCibersegurança6 min readSource: 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers ↗Ler em português →

An old flaw in the NGINX HTTP/2 module can be exploited by attackers without the need for credentials.

NGINX has revealed that the vulnerability identified as CVE-2026-123007, nicknamed "nginx2root", is present in all open-source versions between 1.9.5 (released on September 22, 2015) and 1.31.8. Patches were made available in versions 1.31.9 and 1.30.7, published on November 18, 2026.

Flaw Details

The flaw lies in the handling of HTTP/2 frames when the server is configured with the http2 directive. Under specific conditions—such as the presence of disabled or bypassable ASLR—an attacker can inject code that executes with the privileges of the NGINX worker process. The obtained code initially has the same rights as the worker; escalation to root depends on another Linux kernel vulnerability (SCTP) or privilege escalation techniques.

Demonstrated Exploitation

Wiz researchers confirmed they were able to bypass ASLR and execute arbitrary code in controlled tests. The Xint team demonstrated that, using only an accessible HTTP/2 port, it was possible to inject code that, in Docker environments, could achieve host root privileges by exploiting the Linux kernel SCTP bug.

Impact and Scope

The executed code gains the rights of the NGINX worker, which normally has limited system access. On servers configured with default permissions, this can lead to reading or modifying sensitive files. When combined with the SCTP vulnerability, elevation to root allows full control of the host, including inside Docker containers.

Affected Versions

  • NGINX Open Source 1.9.5 through 1.31.8 (including 1.31.0-1.31.8)
  • NGINX Plus 37.x (up to 37.2.0.1) and releases R34-R36

Linux distributions that package these versions—such as Ubuntu (16.04-26.10) and Debian (bookworm, trixie, forky, sid)—remain vulnerable until the packages are updated.

Patches and Mitigation

Official patches were released in versions 1.31.9 and 1.30.7 for the open-source code, and in versions 37.3.0.1 and 37.0.8.1 for NGINX Plus. It is recommended to:

  1. Immediately update to the patched versions.
  2. Restart NGINX with the new binary (not just reload the configuration).
  3. Disable HTTP/2 (by removing http2 from the listen directive or using http2 off;) until the update is applied.
  4. Disable the Linux kernel SCTP module (for example, by adding install sctp /bin/false in /etc/modprobe.d/).
  5. Avoid using SSI directives, mirror, and constructing server names from variables, mitigating CVE-2026-123634.
  6. Limit the use of NGINX as a mail proxy (CVE-2026-113425) to trusted networks.

Signs of Compromise

CIRCL analysts recommend monitoring for:

  • Worker processes that start unexpected programs or generate core dumps.
  • Long-lived HTTP/2 connections with heavy traffic but few request logs.
  • Unusual outbound connections or DNS queries generated by workers.

These indicators do not confirm exploitation, but may point to abuse attempts.

Next Steps

Organizations still using vulnerable versions should apply patches as quickly as possible, validate the removal of HTTP/2 support, and review kernel security configurations. Until the SCTP bug is fixed, disabling the module reduces the risk of privilege escalation.

CyberX Technical Analysis

The CVE-2026-123007 vulnerability exploits an internal processing flow of the NGINX HTTP/2 module. When the server accepts HTTP/2 connections (http2 or listen ... http2 directive), the vulnerable code allows a specially formatted frame to overwrite critical memory structures, bypassing ASLR on systems where randomization is disabled or can be circumvented.

The injected code executes in the context of the worker process, which normally runs with limited privileges (nginx or www-data user). In Docker environments, the worker still has access to the host namespace, allowing the attacker to escalate privileges to root by exploiting the Linux kernel SCTP vulnerability (CVE-2026-???). This exploitation chain depends on two simultaneous conditions:

  • HTTP/2 enabled and externally accessible.
  • SCTP loaded and vulnerable in the host kernel.

Wiz tests demonstrated that the ASLR bypass can be performed using heap spraying techniques specific to x86-64 CPUs with AVX-512 extensions. Xint showed that, even in Docker containers, code can escape isolation when the vulnerable kernel is present.

From a defense standpoint, the attack surface can be reduced by disabling HTTP/2 until patched versions are in production. In addition, blocking the SCTP module prevents the second escalation phase. Updating to NGINX 1.31.9 or 1.30.7 eliminates the exploitation path on the server itself, removing the memory vulnerability that allows injection.

Specific recommendations:

  1. Immediately apply the patched versions (1.31.9 / 1.30.7 or NGINX Plus equivalents).
  2. Disable HTTP/2 in legacy configurations (listen 443 ssl; instead of listen 443 ssl http2;) until the update is complete.
  3. Check for the presence of the SCTP module (lsmod | grep sctp) and, if present, disable it via install sctp /bin/false in /etc/modprobe.d/.
  4. Review the use of SSI directives, mirror, and dynamic server name construction to mitigate CVE-2026-123634.
  5. Implement worker process and anomalous HTTP/2 traffic monitoring as recommended by CIRCL.

There is no public evidence of exploitation in production; CISA KEV does not yet list the vulnerability. However, the technical severity (CVSS 4.0 9.2) indicates high risk if the attack conditions are met.

CyberX SOC Intelligence Bulletin

The CVE-2026-123007 vulnerability affects NGINX servers with HTTP/2 enabled and allows arbitrary code execution in the worker context, potentially escalating to root via the Linux kernel SCTP bug.

Indicators of Compromise (IoCs)

No verifiable indicators of compromise were identified in the consulted sources. There are no payload samples, hashes, or IP addresses associated with real attacks.

Recommended Mitigations

  • Update immediately to NGINX 1.31.9 (Open Source) or 1.30.7, or equivalent NGINX Plus versions (37.3.0.1 / 37.0.8.1).
  • Disable HTTP/2 in the configuration (http2 off; or remove the http2 directive from listen).
  • Disable the Linux kernel SCTP module (install sctp /bin/false in /etc/modprobe.d/).
  • Avoid using SSI, the mirror directive, and constructing server names from variables to mitigate CVE‑2026‑123634.
  • Limit NGINX as an email proxy or apply firewall rules that restrict access to the service.

Response procedures

  1. Confirm the NGINX version in use (nginx -v) and compare with the list of vulnerable versions.
  2. Apply patches and restart the service with the updated binary (avoid just reload).
  3. Check worker logs for unexpected processes or core dumps.
  4. Monitor long‑duration HTTP/2 connections and anomalous traffic using TLS/HTTP2 analysis tools.
  5. If there is suspicion of exploitation, isolate the host, collect memory evidence, and start forensic investigation per CIRCL guidelines.

Frequently Asked Questions

What is CVE-2026-123007?

It is a vulnerability in the NGINX HTTP/2 module that allows unauthenticated attackers to execute arbitrary code on affected servers by exploiting how HTTP/2 frames are handled.

Which NGINX versions are affected by the flaw?

The vulnerability is present in all open-source NGINX versions between 1.9.5 and 1.31.8.

How can the vulnerability be mitigated?

Organizations should update to NGINX open-source versions 1.31.9 or 1.30.7 (or NGINX Plus versions 37.3.0.1 and 37.0.8.1), disable HTTP/2 support, and review kernel security configurations.

Can the vulnerability lead to root access?

The initial code execution occurs with worker process privileges, but it can escalate to full host root access if combined with a Linux kernel SCTP vulnerability.

Esta análise foi útil?

Ainda não há avaliações.