Cybersecurity Research

Five Critical NGINX Flaws Dubbed 'NGINX2Root' Patched: Restart Required After Upgrade

Sophos · 18 Nov 2026
Key Takeaway Patch NGINX as soon as possible and make sure the service is fully restarted afterwards, because a reload will leave the old vulnerable binary running.

On 18 November 2026, F5 published security advisories for five critical vulnerabilities (CVSS v4.0 score of 9.2) that researchers at Xint have collectively named 'NGINX2Root'. The advisories are K000163925, K000163926, K000163927, K000163928 and K000163931, and they affect both NGINX Open Source and NGINX Plus configurations.

Exploitation could cause crashes, denial of service, memory corruption or code execution. According to F5, code execution requires ASLR (a memory protection feature) to be disabled or bypassed. Two of the flaws relate to how NGINX handles HTTP/2 traffic, and Wiz Research reports they can be used to bypass ASLR. The other three are use-after-free memory flaws that only apply to specific configurations.

Xint reports that each of the five vulnerabilities can be chained with a separate Linux kernel SCTP vulnerability to obtain root privileges on the host, including when NGINX runs in a Docker container.

Organisations should review the F5 advisories and upgrade affected versions. Updated source code and Linux packages for NGINX Open Source are available from the NGINX website, though packages may not be immediately available for older, unsupported distributions. Xint notes that running nginx -s reload does not load the new binary, so NGINX must be restarted or its binary upgraded after updating.

If an immediate upgrade is not possible, F5 advises avoiding SSI or mirror directives and proxied server names that use variables (CVE-2026-123634), and restricting mail proxy listeners to trusted networks (CVE-2026-113425). For the HTTP/2 flaws, Wiz and Xint recommend disabling HTTP/2 on affected listeners, although this may have side effects. Sophos is monitoring for related activity and investigating whether its own products are affected.

Why it matters

Many teams treat a container boundary and ASLR as backstops that limit the damage of a web server bug, but the reported chain with a Linux kernel SCTP flaw undermines both assumptions. Anyone running NGINX as a front door, especially with HTTP/2 enabled, must now consider host-level compromise rather than just a crashed service. The reload caveat also means a routine patch process could appear complete while the vulnerable binary is still running.

What to do

  • Review the F5 advisories K000163925, K000163926, K000163927, K000163928 and K000163931 and upgrade affected NGINX Open Source and NGINX Plus versions.
  • Restart NGINX or upgrade its binary after patching, because nginx -s reload does not load the new binary.
  • Avoid SSI or mirror directives and proxied server names with variables, and restrict mail proxy listeners to trusted networks, if you cannot upgrade immediately.
  • Consider disabling HTTP/2 on affected listeners as a temporary measure, after checking the impact on your services.
NGINX F5 vulnerability patching Docker Linux

Summarised by CISO AI from Sophos, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.