nginx2root.io
NGINX SECURITY RESPONSEFIVE NGINX CVES · ONE SEPARATE KERNEL CHAINREVIEWED 2026-11-19
NGINX2ROOT / SECURITY RESPONSE

Patch NGINX.
Know the path.

Five 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.

/INCIDENT/BRIEF 18 NOV 2026
NGINX OPEN SOURCE / FIXED RELEASES
5 distinct NGINX vulnerabilities
Stable1.30.7
Mainline1.31.9
Root on hostSeparate kernel chain
Distribution packages may carry a backport without changing the upstream version string.
RESPONSE PRIORITIES

Work from the running binary.

Verify the NGINX instance that receives traffic, then the complete package or image build.

RECOMMENDED

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 guide
TEMPORARY

Reduce attack paths.

Disable affected protocols or restrict the relevant resolver and mail proxy configuration while patching.

Review controls
INVESTIGATE

Follow the worker.

Correlate HTTP/2 connection anomalies, worker crashes and unexpected child processes.

Open detection guide
RESEARCH

Read the evidence.

See the public laboratory PoC and why a normal HTTP response is not an exposure test.

Review exploit evidence
FIVE SEPARATE PATHS

Which configuration applies?

Disabling HTTP/2 only addresses the two HTTP/2 CVEs. The other surfaces need their own review.

WORKER ≠ ROOT

Understand the chain.

NGINX entry point

Each CVE is an independent worker-level path with its own prerequisites.

Separate kernel step

Xint chained a Linux SCTP flaw to gain root and escape a container in its test environment.

Patch both layers

Patch NGINX first. Assess the kernel and SCTP exposure separately, following vendor guidance.

Read the exploit evidence