Patch every NGINX build.
Use 1.30.7 stable, 1.31.9 mainline, or a vendor-confirmed backport. Replace running workers and verify the package.
Open patch guideFive NGINX flaws were disclosed on 18 November 2026. Their reachable paths depend on your modules and configuration.
An NGINX worker compromise is serious. Host-root access in Xint’s demo required a separate Linux SCTP kernel flaw.
Verify the NGINX instance that receives traffic, then the complete package or image build.
Use 1.30.7 stable, 1.31.9 mainline, or a vendor-confirmed backport. Replace running workers and verify the package.
Open patch guideDisable affected protocols or restrict the relevant resolver and mail proxy configuration while patching.
Review controlsCorrelate HTTP/2 connection anomalies, worker crashes and unexpected child processes.
Open detection guideSee the public laboratory PoC and why a normal HTTP response is not an exposure test.
Review exploit evidenceDisabling HTTP/2 only addresses the two HTTP/2 CVEs. The other surfaces need their own review.
HTTP/2 flow-control memory corruption. HTTP/2 enabled on a listener.
Read CVE guideHTTP/2 connection use-after-free. HTTP/2 proxying to an upstream under connection pressure.
Read CVE guideResolver use-after-free. Request-triggered DNS resolution with concurrent subrequests.
Read CVE guideHTTP/3 use-after-free. HTTP/3/QUIC proxying to an upstream under connection pressure.
Read CVE guideMail proxy use-after-free. NGINX mail proxy with proxy on and auth_http.
Read CVE guideEach CVE is an independent worker-level path with its own prerequisites.
Xint chained a Linux SCTP flaw to gain root and escape a container in its test environment.
Patch NGINX first. Assess the kernel and SCTP exposure separately, following vendor guidance.