Skip to content
securitytabs

Updated · 2 updates

NGINX HTTP/2 flaws let unauthenticated attackers run code; fixed versions released

Two flaws in the HTTP/2 support of NGINX, widely used web server software, can let an attacker run code on a server without logging in. Fixed versions are out, so administrators of servers with HTTP/2 enabled should update.

NGINX web server memory flaw allows code execution; fix released
NGINX web server memory flaw allows code execution; fix released

What's new

  1. Added Xint Research's disclosure of five NGINX flaws, its kernel-bug chain to root, and reports that no exploitation has been seen. [1][2]

  2. Added the second flaw, CVE-2026-123633 in NGINX Open Source, and the SANS Internet Storm Center's note that F5 patched five NGINX vulnerabilities. [3]

TimelineWhat should my organization do?

Vulnerabilities

What happened

Rapid7 and F5, the company behind NGINX, disclosed CVE-2026-123007 on 18 November. Rapid7 describes it as an integer underflow (an arithmetic error in a counter) in NGINX's HTTP/2 handling. NGINX can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can exploit this by cancelling queued response data, which can lead to memory corruption and code execution in the worker process under certain conditions. [4][5]

NVD lists CVE-2026-123007 against NGINX Plus and a companion flaw, CVE-2026-123633, against NGINX Open Source; both are rated 9.2 on the CVSS v4 scale. Wiz analysed the two together as critical HTTP/2 flaws. The flaw dates to NGINX version 1.9.5, released on 22 September 2015. [4][6][5]

Five flaws, nginx2root

Xint Research disclosed five NGINX vulnerabilities under the name nginx2root, plus one Linux kernel bug, each with a working exploit. The researchers showed the NGINX flaws being chained with the kernel bug to gain root access. Rapid7, Wiz and three other research groups independently found and reported CVE-2026-123633 and CVE-2026-123007. [1][7][2]

Fixes and exploitation

F5 released fixed versions 1.31.9 and 1.30.7 on the day of disclosure. F5 patched five NGINX vulnerabilities in all, and CVE-2026-123007 needs no special configuration beyond HTTP/2 being enabled. [5][3]

CISA has not added either flaw to its list of flaws attackers are known to be using. Help Net Security reports there is no evidence any of the five has been exploited in the wild. [2][3]

Timeline

  1. Xint Research disclosed five NGINX flaws and a kernel bug under the name nginx2root. [1]

  2. Wiz published an analysis of the two NGINX HTTP/2 flaws. [6]

  3. F5 released NGINX versions 1.31.9 and 1.30.7 with the fix. [5]

  4. F5 and Rapid7 disclosed the NGINX HTTP/2 flaw. [4]

Update history

  1. Added Xint Research's disclosure of five NGINX flaws, its kernel-bug chain to root, and reports that no exploitation has been seen. [1][2]

  2. Added the second flaw, CVE-2026-123633 in NGINX Open Source, and the SANS Internet Storm Center's note that F5 patched five NGINX vulnerabilities. [3]

  3. First published

Explained

The technology and terms in this story. Learn more

Business ActionWhat this means inside your organization, and what to do about it, by company size.

Small business

No dedicated security staff; relies on providers

What to know

NGINX often runs behind hosting providers and websites; the risk applies to servers with HTTP/2 enabled. [5]

What to do

  1. Ask your hosting or IT provider whether your sites run NGINX with HTTP/2 enabled. [5]
  2. Ask that NGINX be updated to version 1.31.9 or 1.30.7. [5]

Mid-size company

A small IT or security team

What to know

Two unauthenticated code execution flaws rated 9.2 affect NGINX servers with HTTP/2 enabled; fixed versions exist and no exploitation has been reported. [4][6][2]

What to do

  1. Inventory NGINX servers, both Plus and Open Source, and check which have HTTP/2 enabled. [5][6]
  2. Update to 1.31.9 or 1.30.7 in your next patch window, starting with internet-facing servers. [5]

Large enterprise

A security operations team

What to know

Xint Research says each of the five flaws has a working exploit, though no in-the-wild exploitation is reported. [1][2]

What to do

  1. Find NGINX instances at scale, including those in containers and appliances, and prioritise those exposing HTTP/2. [5]
  2. Read the F5 advisory and the Rapid7 and Wiz analyses for conditions and any mitigations before patching. [4][6]

Sources

  1. [1]Security Affairs · Nov 19, 09:21 UTC
    nginx2root:AI Discovers Five Critical nginx Flaws and a Path to Rootcontext
  2. [2]Help Net Security · Nov 19, 18:25 UTC
    NGINX2Root: F5 patches five critical NGINX vulnerabilitiescontext
  3. [3]SANS Internet Storm Center StormCast · Nov 19, 02:00 UTC
    NGINX2ROOT HTTP/2 RCEs (CVE-2026-123007, CVE-2026-123633); Microsoft Agent Framework PyPI Compromise; Holiday Hack Challenge (Nov 19 2026)context
  4. [4]Rapid7 Blog · Nov 18, 13:56 UTC
    CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)context
  5. [5]The Hacker News · Nov 18, 18:31 UTC
    10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Serverscontext
  6. [6]Wiz Blog · Nov 18, 15:13 UTC
    Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007context
  7. [7]BleepingComputer · Nov 19, 14:57 UTC
    Critical NGINX ‘NGINX2Root’ bugs let attackers hijack serverscontext