Critical CVSS 9.2 Security news

NGINX fixes critical HTTP/2 flaw CVE-2026-123007: memory corruption up to code execution, with a public Rapid7 PoC

The nginx team released versions 1.30.7 and 1.31.9 on 18 November 2026, fixing ten security vulnerabilities. The most serious is CVE-2026-123007 in HTTP/2 flow control: crafted traffic corrupts a worker process's memory and, under certain conditions, allows unauthenticated code execution. Stephen Fewer of Rapid7 found the bug and has published a detailed write-up and a proof-of-concept exploit. No in-the-wild exploitation has been reported. Any nginx with HTTP/2 enabled since version 1.9.5 is affected.

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

Critical: NGINX, CVE-2026-123007, CVSS 9.2

Key points

  • Who is affected: web servers, reverse proxies and load balancers running nginx or NGINX Plus with HTTP/2 enabled, which is the norm for HTTPS sites.
  • The flaw: an integer underflow in HTTP/2 flow control leads to an out-of-bounds write in the worker process. The result is a worker crash, data disclosure or code execution with the worker's privileges.
  • Exploited: no, but a public PoC exists. According to Rapid7 the attack needs around 128 GB of traffic over a single connection and a specific CPU and glibc combination.
  • What to do: upgrade to 1.30.7/1.31.9, watch your distribution's packages and consider disabling HTTP/2 until patched. The same release fixes nine other flaws.

Vulnerabilities: CVE-2026-123007

What happened

On 18 November 2026 the nginx team at F5 released stable nginx 1.30.7 and mainline 1.31.9. According to the security advisories page, they fix ten vulnerabilities. The most serious is CVE-2026-123007, memory corruption in HTTP/2 flow control, which nginx rates as "major". In the NVD record, F5 scores it 9.2 under CVSS 4.0 and 8.1 under CVSS 3.1.

The bug was found by Stephen Fewer of Rapid7, who published a detailed analysis and a proof-of-concept exploit the same day. Neither Rapid7 nor the CVE description mentions exploitation in the wild.

Technical details

HTTP/2 controls data flow with a "window": how many bytes the server may send before the client grants more credit with a WINDOW_UPDATE frame. Rapid7 explains that nginx stores the connection-level window as an unsigned value and, when cleaning up a finished request, restores credit without checking the protocol maximum. A change to SETTINGS_INITIAL_WINDOW_SIZE also resets only the affected streams rather than closing the connection. A later check then underflows (CWE-191), and the bogus response length travels down to the TLS send path, where it causes an out-of-bounds write (CWE-787).

F5's NVD description names a worker process crash as the usual outcome, with code execution possible where ASLR is disabled or bypassed. Rapid7 demonstrated code execution with the worker process's privileges (not root) on x86-64 Linux. Rapid7's conditions: HTTP/2 and TLS enabled, roughly 128 GB of traffic over one connection, a fast direct link (connections end after the default hour), and a CPU with AVX-512, which makes glibc pick an exploitable memory-copy routine. It is a data plane issue only; the NGINX Plus management interface is not exposed.

Who is affected

Product Vulnerable Fixed
nginx Open Source (stable) 1.9.5–1.30.6 1.30.7
nginx Open Source (mainline) 1.31.0–1.31.8 1.31.9
NGINX Plus 37.1.0–37.2.0.1 37.3.0.1
NGINX Plus 37.0.0–37.0.7.1 37.0.8.1
NGINX Plus R34–R36 no fix listed

Only configurations using HTTP/2 (http2 on; or the http2 parameter on listen) are affected. The same release fixes nine other flaws, including a major infinite loop when reading a request body over TLS 1.3 (CVE-2026-118899) and a use-after-free in the mail proxy (CVE-2026-113425), plus bugs in HTTP/3, the resolver, PROXY protocol v2, alias with try_files and the stream module.

How to tell if you were compromised

Neither F5 nor Rapid7 has published indicators of compromise. What we would watch:

  • Worker process crashes in the error log (worker process … exited on signal 11), especially repeated crashes after long HTTP/2 connections.
  • Unusually large data volumes on a single connection (tens to hundreds of GB) from one IP address, particularly with a high number of WINDOW_UPDATE frames.
  • Child processes of an nginx worker (a shell, curl, wget) in EDR or auditd; nginx does not normally spawn any.

What to do

  1. Upgrade to nginx 1.30.7 or 1.31.9, and NGINX Plus to 37.0.8.1 or 37.3.0.1. For distribution packages, follow your distribution's advisory for CVE-2026-123007.
  2. Consider disabling HTTP/2 until patched: http2 off; (nginx 1.25.1 and later), or remove the http2 parameter from listen on older versions. Clients fall back to HTTP/1.1.
  3. NGINX Plus R34–R36 has no fix according to Rapid7, so plan a move to the 37 branch.
  4. After upgrading, check the version (nginx -v), make sure new processes are running (nginx -t, then restart) and review the error log for the past few days.

Timeline

Timeline of nginx flaw CVE-2026-12300711 Nov 2026: Rapid7 contacts F5; 12 Nov 2026: Rapid7 sends F5 the vulnerability details; 16 Nov 2026: F5 confirms the bug, assigns a CVE and sets the disclosure date; 18 Nov 2026: nginx 1.30.7 and 1.31.9, Rapid7 write-up and PoC, NVD record11 Nov 2026Rapid7 contacts F512 Nov 2026Rapid7 sends F5 thevulnerability details16 Nov 2026F5 confirms the bug, assignsa CVE and sets the disclosuredate18 Nov 2026nginx 1.30.7 and 1.31.9,Rapid7 write-up and PoC, NVDrecord
From report to fix (Rapid7, nginx.org, NVD)

Update

  • 18 Nov 2026: first version.

FAQ

How do I check which nginx version I run?

Run nginx -v on the server. Versions 1.30.7 (stable) and 1.31.9 (mainline) and later are fixed. If you use your distribution's package (Debian, Ubuntu, RHEL), it may carry an older version number with a backported fix, so check your distribution's advisory for CVE-2026-123007.

Is the attack realistic if it needs 128 GB of data?

It is demanding, not impossible. In Rapid7's lab, code execution took about two and a half minutes. The attacker needs a fast direct connection to the server (roughly 300 Mbit/s or more according to Rapid7, otherwise the connection hits the default one-hour limit), and the working exploit relies on CPUs with AVX-512. Crashing worker processes may not need those conditions, so do not delay the upgrade.

Am I protected if nginx sits behind Cloudflare or another proxy?

Partly. Rapid7 says attacker-crafted HTTP/2 frames would probably not survive a proxy that re-encodes traffic in a usable form. But origin servers are often reachable directly by IP address as well, so patch them anyway.

Sources

  1. nginx.org – nginx security advisories
  2. nginx.org – news: nginx 1.30.7 and 1.31.9 (18 Nov 2026)
  3. NVD – CVE-2026-123007
  4. Rapid7 – CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (18 Nov 2026)
  5. F5 – security advisory K000163926

Spotted a mistake? Let us know and we will correct it openly.