NGINX2Root Flaws Enable Unauthenticated Code Execution; Patches and Workarounds Available

· Original article ↗

Summary

Five configuration-dependent NGINX flaws can enable unauthenticated code execution. F5 released fixes, and a public PoC exists for CVE-2026-123007; no in-the-wild exploitation had been reported by November 19, 2026.

Key points

  • NGINX2Root comprises five memory-safety flaws that can allow unauthenticated code execution as an NGINX worker; exposure depends on enabled features.
  • Affected features include HTTP/2, HTTP/3, request-time DNS resolution, and the mail proxy. F5 rates the flaws Critical under CVSS v4.0.
  • F5 released fixes for NGINX Open Source 1.30.7 and 1.31.9, and NGINX Plus 37.0.8.1 and 37.3.0.1; upgrading requires a full restart.
  • A public proof of concept for CVE-2026-123007 appeared on November 18, 2026. Its author reports unauthenticated code execution in a specific Docker lab setup and notes significant exploit constraints.
  • Researchers report chaining an NGINX foothold with an unpatched Linux kernel SCTP bug to reach host root; technical details were withheld, and no kernel fix was available at disclosure.
  • No in-the-wild exploitation had been reported as of November 19, 2026. Temporary mitigations include disabling affected features and blocking SCTP where unused; upgrading is the complete fix.

Article Details

Vulnerability Types
  • Memory safety
  • Memory corruption
  • Use-after-free
  • Double-free
Severity
F5 rates each of the five NGINX flaws 9.2 (Critical) under CVSS v4.0 and 8.1 (High) under CVSS v3.1.
Affected Versions
  • NGINX Open Source 0.5.33–1.31.8, depending on the flaw and configuration
  • NGINX Plus R33–R36 and 37.x builds before the applicable fixed releases
Exploitation Status
not_reported
Exploit Availability
public_poc
Patch Status
available
Workarounds
  • Disable HTTP/2 by removing http2 from listen directives; on NGINX 1.25.1 and later, also set http2 off.
  • Disable HTTP/3 by removing QUIC listeners, setting http3 off, and sending an Alt-Svc header set to clear.
  • Use a static upstream block for proxy_pass instead of a hostname derived from the request.
  • Keep mail-proxy listeners on loopback or firewall them off from untrusted networks.
  • On hosts that do not need SCTP, block the module with install sctp /bin/false; an already-loaded module remains active until reboot or removal.

MITRE ATT&CK

CVE

Vendors

Products

Related Articles