Critical nginx vulnerabilities disclosed. Immediate action recommended.
If you run nginx, check whether your servers are affected and update to the patched version immediately. If you cannot upgrade, follow the mitigation guidance at https://nginx2root.com
Today we’re disclosing nginx2root, five distinct vulnerabilities in one of the world’s most widely deployed web servers, each capable of unauthenticated remote code execution under affected conditions. One of these vulnerabilities affects nginx’s most common configuration. We’ve also demonstrated a fully remote, unauthenticated exploit chain that escalates from nginx RCE to root access on the underlying server, using a separate Linux kernel vulnerability.
Why this is so important:
One of these bugs has been hiding in nginx’s HTTP/2 implementation since 2015. That’s more than a decade in software that powers roughly a third of the web. Every official release from 1.9.5 through 1.31.8 contains the vulnerable code, including the master branch as of Nov 10, 2026.
A Xint researcher found the specific vuln that hits nginx in its default config. This discovery was around the same time he found another critical vulnerability in a different project that we cannot talk about yet due to the same concerns as nginx2root. We took those learnings and incorporated them into the harness as a new, general Xint feature (that is, not fine-tuned to nginx), which then found the other 4 critical nginx vulnerabilities with no human guidance.
We coordinated disclosure with the nginx maintainers and major cloud providers to help make fixes available before publication.
Technical details, affected versions, and remediation guidance:
https://nginx2root.com