Where the path begins.
Request-triggered DNS resolution with concurrent subrequests. The upstream range above is from nginx.org; distribution backports and vendor builds require their own package advisory.
Simultaneous resolution of the same name in subrequests can leave resolver state in use after release.
Replace the running binary.
Update to NGINX Open Source 1.30.7 stable, 1.31.9 mainline or a vendor-confirmed backport. Restart or complete a supported live binary upgrade. A config reload alone does not load the new executable.
Temporary control: Remove the affected request-time resolution path; use fixed upstreams where feasible. This is scoped to this path and is not a substitute for patching all affected components.
See control detailsWhat research establishes.
nginx.org identifies the affected upstream release range and fixed builds. Xint describes this configuration-specific attack path. NGINX worker execution is distinct from host-root access, which required a separate kernel flaw in Xint's demonstration.
No public PoC is linked here for this CVE. Xint reports laboratory exploitability; check its research for details.