Researchers Detail Two Critical HTTP/2 RCE Flaws in NGINX

· Original article ↗

Summary

Researchers disclosed two critical NGINX HTTP/2 flaws, CVE-2026-123633 and CVE-2026-123007, that can enable unauthenticated remote code execution. F5 released fixes; disable HTTP/2 temporarily if upgrades are delayed.

Key points

  • Both vulnerabilities require HTTP/2 to be enabled and can allow unauthenticated code execution on affected NGINX servers.
  • CVE-2026-123633 is a use-after-free that can occur when a connection is closed while a request is still being processed.
  • CVE-2026-123007 is an HTTP/2 flow-control integer underflow that can lead to an out-of-bounds memory copy.
  • Wiz confirmed remote code execution in testing, including on NGINX 1.31.7 and 1.31.8; the second flaw was demonstrated with ordinary static files.
  • F5 released fixes, including NGINX OSS 1.30.7 stable and 1.31.9 mainline releases for both flaws.
  • If an immediate upgrade is not possible, the researchers recommend temporarily disabling HTTP/2 on affected instances.

Article Details

Attack Vectors
  • An unauthenticated attacker who can communicate directly with an affected NGINX server can exploit either vulnerability over HTTP/2. CVE-2026-123633 affects reverse-proxy processing when connection slots run low: an HTTP/2 connection remains marked reusable while a request is processing, allowing it to be closed and freed while the request still uses it.
  • CVE-2026-123007 can be triggered by sending many HTTP/2 WINDOW_UPDATE records. Incorrect flow-control accounting can underflow the send-window check and lead to an out-of-bounds memory copy and remote code execution.
Defensive Notes
  • Identify affected NGINX deployments with HTTP/2 enabled and upgrade to a release that fixes both vulnerabilities as soon as available. The article lists NGINX OSS fixed releases as 1.30.7 stable and 1.31.9 mainline, and NGINX Plus fixed releases as 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007.
  • If an upgrade is not immediately possible, temporarily disable HTTP/2 on affected instances. On NGINX 1.25.1 or later, set `http2 off;` in affected server blocks and remove the `http2` parameter from listen directives. Test compatibility, reload NGINX, and confirm old workers have exited; re-enable HTTP/2 after upgrading.
  • Investigate unexpected NGINX worker crashes or commands launched by NGINX, which the article describes as general warning signs rather than confirmed indicators of these vulnerabilities.
  • For CVE-2026-123007, detection rules for long-lived HTTP/2 connections sending large amounts of data may provide a hint of associated attack activity.

MITRE ATT&CK

CVE

Vendors

Products

Tools

Related Articles