Technology1 min read

Pre-auth RCE in Nginx HTTP/2 handling

By · Published by Everything Blog

In short

The two flaws, designated CVE-2026-123633 and CVE-2026-123007, enable remote code execution, website defacement, and data theft by unauthenticated threat actors. Researchers confirmed that one vulnerability allows full server compromise even on systems that only deliver static files without dynamic backends or custom modules. Wiz Research uncovered the vulnerabilities using its Wiz Atlas harness and validated them with Gemini 4 Carbon and ChatGPT 5.6 Sol. Organizations using HTTP/2 traffic on NGINX are urged to apply the newly available vendor patches.

Key points

  • Systems serving purely static content remain fully vulnerable to unauthenticated remote c…: Systems serving purely static content remain fully vulnerable to unauthenticated remote code execution.
  • Both security flaws carry a severe CVSS 4.0 score of 9.2 due to their potential for compl…: Both security flaws carry a severe CVSS 4.0 score of 9.2 due to their potential for complete host takeover.
  • Administrators operating NGINX deployments with HTTP/2 enabled must immediately install t…: Administrators operating NGINX deployments with HTTP/2 enabled must immediately install the coordinated security updates from F5.

Sources checked by our analysis pipeline: 1

Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered two critical remote code execution vulnerabilities in NGINX, software used to receive and route traffic to production applications and APIs.

Successful exploitation could let attackers take control of affected NGINX servers, steal sensitive data, tamper with websites, or disrupt services.

The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2. The flaws are in NGINX itself. Websites and APIs can be exposed even when their own application code is secure. Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server. Additional conditions are described below. CVE-2026-123007 affects versions dating back to NGINX 1.9.5 in 2015.

We reported our findings to F5, the company behind NGINX, and collaborated with its security team on remediation and coordinated disclosure. Organizations should identify affected deployments and apply the security updates when released.

We recommend updating affected NGINX deployments to the latest release which includes multiple security fixes.

Responsible disclosure timeline

October 21, 2026: Wiz reports the HTTP/2 use-after-free vulnerability, later assigned CVE-2026-123633, to F5,…

Technology