Mitigating NGINX2Root (CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, CVE-2026-113425) on Rocky Linux 8, 9, and 10

Arsalan Zaidi
Customer Support Engineering Lead

Introduction

NGINX2Root is a collection of five critical vulnerabilities in the nginx web server disclosed on 2026-11-18. Four are use-after-free flaws (CWE-825) and one is a heap-based buffer overflow (CWE-787). All five can lead to remote code execution on systems running affected nginx configurations. A public proof-of-concept exploit exists for CVE-2026-123007.

Each vulnerability targets a different nginx subsystem, so the exposure profile depends on which nginx features are enabled:

CVE Component CWE CVSS 3.1 Trigger Condition
CVE-2026-123007 HTTP/2 flow control CWE-787 (heap overflow) 8.1 HTTP/2 enabled on any listen directive
CVE-2026-123633 HTTP/2 reverse proxy CWE-825 (UAF) 8.1 HTTP/2 enabled with reverse proxy, low connection slots
CVE-2026-121810 HTTP/3 (QUIC) CWE-825 (UAF) 8.1 HTTP/3 (QUIC) enabled (experimental module)
CVE-2026-123634 Resolver + SSI/mirror CWE-825 (UAF) 8.1 Dynamic server names with resolver plus SSI or mirror
CVE-2026-113425 Mail proxy CWE-825 (UAF) 8.1 mail {} block present in configuration

The two broadest CVEs are CVE-2026-123007 and CVE-2026-123633, which affect any nginx deployment with HTTP/2 enabled. HTTP/2 is enabled by default in many nginx configurations and is the most common deployment pattern for HTTPS traffic.

CVE-2026-123007 is especially severe: it has been present in nginx since version 1.9.5 (2015), and a working Rapid7 exploit is publicly available.

Problem

Rocky Linux ships nginx in AppStream as a base package and through module streams. Every nginx version currently shipped is within the affected range for at least some of the five CVEs:

Rocky Linux Version nginx Versions Affected CVEs
Rocky Linux 10 (el10) nginx 1.26+ All five: CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, CVE-2026-113425
Rocky Linux 9 (el9) nginx (base), nginx:1.24 stream CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-113425 (not CVE-2026-121810, since these builds lack HTTP/3)
Rocky Linux 9 (el9) nginx:1.26 stream All five (1.26 includes HTTP/3 support)
Rocky Linux 8 (el8) nginx:1.24 stream CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-113425 (not CVE-2026-121810)

Treat the following CIQ variants as affected:

  • RLC Pro 10 and CIQ SIG/Cloud Next 10
  • RLC Pro 9 and CIQ SIG/Cloud Next 9
  • RLC Pro LTS 9.2 and 9.6
  • RLC Pro LTS 8.6 and 8.10
  • RLC Pro 8 and CIQ SIG/Cloud Next 8
  • RLC Pro FIPS and RLC Pro Hardened variants across all versions

CIQ Bridge does not ship nginx. If nginx is present on a CentOS 7 system, it was installed from a third-party source and is outside the scope of CIQ support.

For community Rocky Linux editions, refer to Rocky Linux Errata.

Systems that do not have nginx installed are not affected. Systems where nginx is installed but not running are not exploitable, though they should still be patched when updates are available.

Status

  • No patched nginx packages are available yet. CIQ is building patched packages for all supported variants. This article will be updated with package versions as they become available.
  • Configuration-based mitigations are available for all five CVEs. See the Mitigation section below. Apply the relevant mitigations immediately on internet-facing systems.
  • A public exploit exists for CVE-2026-123007 (Rapid7). No confirmed in-the-wild exploitation has been reported as of 2026-11-19.
  • All five vulnerabilities are remotely exploitable. No authentication on the target system is required. The attacker needs only network access to the nginx listener.
  • CVSS 3.1 base score: 8.1 for all five CVEs (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Rated Critical for CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425. Rated Important for CVE-2026-123634.
  • Upstream fix: nginx 1.30.7 (stable) and 1.31.9 (mainline) contain fixes for all five CVEs.
  • Open a support case if you need help confirming exposure, assessing mitigation impact, or tracking patched package availability for a specific CIQ variant.

Patched Packages

No patched nginx packages are available from CIQ as of 2026-11-19. This table will be updated as builds are released.

Variant Patched Package Version Repository Released
pending pending pending pending

Confirm the installed nginx version on a given system with:

nginx -v
rpm -q nginx

Confirming Exposure

Each CVE has a specific trigger condition. Check which conditions apply to your nginx deployment.

HTTP/2 (CVE-2026-123007, CVE-2026-123633)

These are the broadest and most critical. Check whether HTTP/2 is enabled:

grep -rn 'http2' /etc/nginx/ 2>/dev/null
grep -rn 'listen.*http2' /etc/nginx/ 2>/dev/null

Any listen directive containing http2 or any http2 on; directive means the system is exposed to both CVEs. CVE-2026-123633 additionally requires nginx to be configured as a reverse proxy (proxy_pass directives present), but CVE-2026-123007 affects all HTTP/2 configurations including static file serving.

HTTP/3 / QUIC (CVE-2026-121810)

This only applies to nginx builds with HTTP/3 support (Rocky Linux 10, or the nginx:1.26 module stream on Rocky Linux 9):

grep -rn 'quic\|http3' /etc/nginx/ 2>/dev/null

Any listen directive containing quic or any http3 on; directive means the system is exposed.

Resolver with SSI or mirror (CVE-2026-123634)

This requires a specific combination: nginx must be configured as a proxy that uses a resolver directive for dynamic backend hostname lookup, combined with either SSI (ssi on;) or the mirror directive:

grep -rn 'resolver\b' /etc/nginx/ 2>/dev/null
grep -rn 'ssi on\|mirror' /etc/nginx/ 2>/dev/null

If both a resolver and either ssi on or mirror are present, the system may be exposed. Static proxy configurations where backend addresses are resolved at startup are not affected.

Mail proxy (CVE-2026-113425)

This requires a mail {} block in the nginx configuration:

grep -rn '^\s*mail\s*{' /etc/nginx/ 2>/dev/null
nginx -T 2>/dev/null | grep -c 'mail {'

If a mail context is present, the system is exposed. The mail module uses auth_http for authentication, and all ngx_mail_* modules depend on it.

Mitigation

Apply the relevant mitigations below based on which features are enabled. Each mitigation targets one or more CVEs. After making configuration changes, reload nginx:

sudo nginx -t && sudo systemctl reload nginx

Disable HTTP/2 (mitigates CVE-2026-123007 and CVE-2026-123633)

This is the highest priority mitigation since HTTP/2 is the broadest attack surface and a public exploit exists.

For nginx 1.25.1 and later (Rocky Linux 10, nginx:1.26 stream on Rocky Linux 9), add or set the following in the http or server context:

http2 off;

Also remove the http2 parameter from any listen directives:

# Before:
listen 443 ssl http2;

# After:
listen 443 ssl;

For nginx versions before 1.25.1 (Rocky Linux 8, base nginx on Rocky Linux 9), remove the http2 parameter from listen directives. The http2 off; directive is not available in these versions.

⚠️ WARNING Disabling HTTP/2 forces all HTTPS clients to fall back to HTTP/1.1. This can affect performance for applications that rely on HTTP/2 multiplexing. Web browsers and API clients will continue to function over HTTP/1.1, but throughput for concurrent requests may decrease. Assess the performance impact in your environment before deploying broadly.

Disable HTTP/3 / QUIC (mitigates CVE-2026-121810)

Remove the quic parameter from listen directives and disable HTTP/3:

# Before:
listen 443 quic;

# After:
listen 443 ssl;

Add or set in the http or server context:

http3 off;

The performance impact of disabling HTTP/3 is minimal in most deployments, since HTTP/3 is an experimental feature and few clients negotiate it by default.

Disable dynamic resolver with SSI/mirror (mitigates CVE-2026-123634)

If your configuration uses a resolver directive for dynamic backend hostname lookup combined with ssi on; or mirror, disable either the SSI/mirror feature or switch to static backend addresses.

To disable SSI:

# Comment out or remove:
# ssi on;

To disable mirror:

# Comment out or remove:
# mirror /mirror_target;
# mirror_request_body on;

Alternatively, replace dynamic hostname resolution with explicit IP addresses in proxy_pass directives, which removes the resolver dependency.

Restrict or disable mail proxy (mitigates CVE-2026-113425)

If the mail {} block is not needed, remove it entirely from the configuration.

If the mail proxy must remain active, restrict access to mail ports (25, 143, 993, 995, 587) to trusted clients only using firewall rules:

sudo firewall-cmd --permanent --remove-service=smtp
sudo firewall-cmd --permanent --remove-service=imap
sudo firewall-cmd --permanent --remove-service=imaps
sudo firewall-cmd --permanent --remove-service=pop3s
sudo firewall-cmd --reload

Then add specific rules to allow only trusted source IPs. This reduces the attack surface but does not fully eliminate the vulnerability.

Verification

After applying mitigations, confirm they are in effect.

HTTP/2 disabled:

nginx -T 2>/dev/null | grep -E 'http2|listen.*http2'

No output means HTTP/2 is disabled. If http2 off; appears, it is explicitly disabled (correct). If listen ... http2 or http2 on; still appears, the mitigation is not in effect.

HTTP/3 disabled:

nginx -T 2>/dev/null | grep -E 'quic|http3'

No output or http3 off; means HTTP/3 is disabled.

Old workers replaced:

After reloading, confirm that no old worker processes are still running. Old workers continue serving existing connections with the previous configuration:

ps aux | grep 'nginx: worker'

If old workers persist, a full restart will terminate them:

sudo systemctl restart nginx

Installing the Update

Once patched packages are available, install the update and restart nginx. A configuration reload (systemctl reload) does not replace the running nginx binary; a full restart is required.

sudo dnf update nginx*
sudo systemctl restart nginx

Confirm the updated version:

nginx -v
rpm -q nginx

After installing the patched package and restarting, revert any mitigations (re-enable HTTP/2, HTTP/3, etc.) and reload:

sudo nginx -t && sudo systemctl reload nginx

Vulnerability Details

CVE-2026-123007: HTTP/2 flow control integer underflow

The connection-level send_window counter in the HTTP/2 implementation can be manipulated past its maximum value. When a client cancels a stream, the unsent data allowance is refunded to the connection window without checking the HTTP/2 maximum. If the client raised the window via WINDOW_UPDATE frames while data was queued, the refund pushes the counter past the bound. Because the overflow check uses unsigned subtraction, further WINDOW_UPDATE frames are accepted, inflating the counter to an arbitrary value. The resulting negative value in the TLS send path produces a buffer with reversed start and end pointers, leading to an out-of-bounds memory copy. This can be leveraged for memory disclosure, heap corruption, and code execution.

Present in nginx since version 1.9.5 (2015). Affects all nginx builds with HTTP/2 support.

CVE-2026-123633: HTTP/2 connection use-after-free

When a partial HEADERS frame arrives on an HTTP/2 connection with no active streams, nginx marks the connection as reusable while waiting for the rest of the frame. When the remaining data arrives and a stream is created, the connection is not removed from the reusable list. If upstream connection allocation runs low, ngx_drain_connections() may select the still-listed connection for cleanup during its own request. The error path frees the connection memory, but request processing continues using stale pointers. The freed memory can be reallocated with attacker-controlled data.

Present in nginx since version 1.19.7. Affects nginx deployments configured as HTTP/2 reverse proxies.

CVE-2026-121810: HTTP/3 (QUIC) use-after-free

A use-after-free in the experimental HTTP/3 (QUIC) processing path. Can crash worker processes or lead to code execution if memory protections are bypassed. Only affects nginx builds compiled with HTTP/3 support (Rocky Linux 10, or the nginx:1.26 module stream on Rocky Linux 9).

CVE-2026-123634: Resolver use-after-free with SSI or mirror

A use-after-free in the DNS resolver when nginx is configured as a proxy with dynamic server names combined with SSI or the mirror directive. Can lead to code execution, memory corruption, or denial of service. This requires a specific, less common configuration pattern.

CVE-2026-113425: Mail proxy use-after-free

A use-after-free in the nginx mail proxy server. Can crash the worker process or allow code execution. Affects any nginx deployment with a mail {} block in its configuration. All ngx_mail_* modules depend on mail_auth_http.

Notes

  • This is a userspace vulnerability, not a kernel issue. The fix is a package update and service restart. No system reboot is required.
  • A configuration reload is not sufficient after patching. After installing the updated package, run systemctl restart nginx (not just reload) to replace the running binary. A reload only re-reads the configuration; the old, vulnerable binary continues handling requests.
  • Containers running nginx need separate updates. If your environment runs nginx inside containers (Podman, Docker, Kubernetes), each container image must be rebuilt with the patched nginx package. Host-level updates do not affect containerized nginx instances.
  • Reverse proxies and CDNs may provide partial protection. If a CDN or load balancer terminates HTTP/2 before traffic reaches nginx, the HTTP/2 CVEs (CVE-2026-123007, CVE-2026-123633) may not be reachable. However, this depends on the CDN's implementation and should not be relied upon as a primary mitigation.