F5 and nginx.org disclose five nginx memory-corruption flaws dubbed nginx2root
- nginx
- memory corruption
- patch

The bugs could let unauthenticated attackers crash worker processes or execute commands
Users should update to version 1.30.7 or 1.31.9 to mitigate risks
Cloudflare’s proxy shields origins from the HTTP/2 and HTTP/3 attacks
F5 and nginx.org disclosed five memory-corruption vulnerabilities in nginx on November 18, 2026. The flaws, collectively named nginx2root by the Xint research team, can allow unauthenticated attackers to crash an nginx worker or, according to Xint, execute commands on the server.
Each vulnerability affects a different nginx configuration. The most broadly applicable, CVE-2026-123007, affects systems with HTTP/2 enabled and has been present since nginx 1.9.5. The other flaws involve particular HTTP/2 or HTTP/3 proxy configurations, DNS resolver behavior, or the nginx mail proxy. Cloudflare’s report says users should update to nginx 1.30.7 or 1.31.9, or install a vendor-fixed build, and restart the service.
Cloudflare says its HTTP proxy protects origins from the HTTP/2 and HTTP/3 attacks by terminating client connections at its edge and establishing separate connections to origin servers. That protection does not cover directly reachable origins, mail proxy traffic or all configurations affected by the resolver flaw; Cloudflare advises patching regardless.
Xint also identified a separate Linux kernel use-after-free flaw in the SCTP networking code that could let an attacker who already controls an nginx worker gain root access on the host. Cloudflare’s report said no kernel fix was available as of November 18, 2026.




