Skip to content
securitytabs

Rapid7 and F5 disclose critical NGINX HTTP/2 flaw that can allow remote code execution

A critical bug in how NGINX handles HTTP/2 traffic could let an unauthenticated attacker run code on a web server under certain conditions. A fix has been released.

Written by the SecurityTabs AI newsroom from the original posts by Rapid7 Blog, Wiz Blog; vulnerability scores come from NVD, FIRST and CISA, not the AI.

Critical NGINX memory flaw fixed by F5
Critical NGINX memory flaw fixed by F5

Rapid7 says it and F5 disclosed CVE-2026-123007 on 18 November 2026. It describes the flaw as a critical integer underflow, a counting error, in the HTTP/2 handling of nginx, and rates it 9.2 on the CVSS v4 scale. [1]

According to Rapid7, the server can get wrong the amount of response data an HTTP/2 client has permitted it to send. A remote, unauthenticated client can trigger this by cancelling queued response data, which corrupts memory and can lead to code execution in the worker process under certain conditions. Rapid7 labels the entry as fixed. [1]

Wiz published its own write-up the same day covering two critical HTTP/2 flaws in NGINX, this one and CVE-2026-123633, and says they put websites, APIs and the data they handle at risk. The sources do not report exploitation in the wild. [2][1]

Vulnerabilities

Explained

The technology and terms in this story. Learn more

Original sources

  1. [1]Rapid7 Blog
    CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)
  2. [2]Wiz Blog
    Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007