Cloud & DevOpsSecurity

NGINX HTTP/2 RCE: Patch CVE-2026-123633 and CVE-2026-123007 Now

F5 shipped a security release for NGINX on November 18 that patches five critical vulnerabilities — two of them unauthenticated remote code execution flaws in HTTP/2 rated CVSS 9.2. The bundle is called NGINX2Root, and with roughly one-third of the web running NGINX, the blast radius is large. Proof-of-concept exploits are already circulating. If you have NGINX in production with HTTP/2 enabled, the action item is straightforward: upgrade now.

Two CVEs You Need to Know

CVE-2026-123633 is a use-after-free in NGINX’s HTTP/2 connection handling. The root cause is subtle: NGINX registers HTTP/2 connections in an idle pool even after a request starts on them. When a worker process runs low on connections, NGINX recycles from that pool — including live ones. An attacker can fragment HEADERS frames to trigger the free and then exploit the dangling pointer. The preconditions are HTTP/2 enabled, upstream proxying configured, and a worker process under connection pressure. That describes most production setups.

CVE-2026-123007 is an integer underflow in HTTP/2 flow control accounting. Invalid window values propagate into heap writes, leading to memory corruption and RCE. The only precondition is HTTP/2 enabled on a listening port — no proxy required. This one has been in the codebase since HTTP/2 support landed in NGINX 1.9.5 in 2015. Eleven years, undetected.

Both vulnerabilities require no authentication. Port 443, unauthenticated, remote code execution. That combination puts these at the top of the patch queue.

Who Is Affected

CVE-2026-123633 affects NGINX Open Source versions 1.19.7 through 1.31.8 when HTTP/2 is enabled and upstream proxying is in use. CVE-2026-123007 goes back further — 1.9.5 through 1.31.8 — and only requires HTTP/2 to be on. Modern TLS configurations enable HTTP/2 by default, so the majority of internet-facing NGINX deployments are in scope for at least one of these. That is more than 225 million websites.

Patch First, Workaround Second

The fix is straightforward. Upgrade to NGINX Open Source 1.30.7 (stable branch) or 1.31.9 (mainline). For NGINX Plus, the fixed releases are 37.0.8.1 and 37.3.0.1.

One caveat for distro-packaged NGINX: package repositories on RHEL, Debian, Ubuntu, and others will likely lag behind the official NGINX release. If your version manager returns something older than 1.30.7, install from the official NGINX repository directly.

Check your current version with:

nginx -v

If you cannot upgrade immediately, disabling HTTP/2 blocks the known attack paths for CVE-2026-123633 and CVE-2026-123007. For NGINX 1.25.1 and later:

http {
    http2 off;
    server {
        listen 443 ssl;
        # ...
    }
}

For older versions, remove the http2 parameter from your listen directives:

# Before:
listen 443 ssl http2;

# After:
listen 443 ssl;

Apply changes with:

nginx -t && nginx -s reload

Two important caveats with the workaround. First, it only covers two of the five NGINX2Root vulnerabilities — it is not a substitute for patching. Second, if you proxy gRPC through NGINX, disabling HTTP/2 breaks those routes. Patch; do not leave the workaround in place indefinitely.

How These Were Found

Xint, an AI security startup, ran their automated analysis harness against NGINX’s C source code and found four of the five NGINX2Root bugs in 90 minutes across 50,000 lines — with no human researcher guiding the scan. This is the same week an AI tool surfaced Java4Shell (CVE-2026-114938) in OpenJDK. The pattern is consistent: AI is finding vulnerabilities that sat undetected in mature, widely-audited codebases for years.

The practical implication for anyone running infrastructure: the time between a bug being introduced and it being discovered is shrinking. So is the window between a patch dropping and exploit code appearing. CVE-2026-123007 existed for 11 years before Xint found it; the PoC appeared within hours of the patch. The Tenable FAQ has a full breakdown of all five CVEs if you want the complete picture. Treat security updates as operational tasks with SLAs, not backlog items.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *