Xint Discloses Five nginx Flaws Chainable to Host Root

Original title: NGINX2Root by Xint – From Nginx visitor to root of the server host
88AI Score

Security firm Xint disclosed five nginx vulnerabilities plus a Linux kernel SCTP flaw, each with a proven exploit. The most severe, an nginx HTTP/2 flow-control bug, lets unauthenticated remote attackers corrupt worker memory and leak addresses, and chaining it with the kernel flaw yields remote host root. Affected versions span nginx 1.9.5 through 1.31.8, fixed in 1.31.9.

Full Report

Contents24 sections

What is NGINX2Root?

TL;DR

nginx2root is a collection of five distinct nginx vulnerabilities and one Linux kernel vulnerability. Each has a proven exploit. The most severe enables unauthenticated remote code execution;

chained with a separate Linux kernel vulnerability, it can lead to host root.

Severity Critical

Access Remote, no authentication

Affected nginx 1.9.5 – 1.31.8

Fix 1.31.9

Five nginx findings and one kernel vulnerability

Each CVE has its own proven exploit. The most severe of the five allows unauthenticated remote code execution on web servers running a common nginx configuration. This remote code execution can be chained with a separate Linux kernel vulnerability to reach host root, remotely and without authentication.

nginx · 5 findings 5 / 5 exploits proven

CVE-2026-123007CVE-2026-123634CVE-2026-123633CVE-2026-121810CVE-2026-113425

Linux kernel · SCTP Exploit proven

Chained result Host root · remote, unauthenticated

Demonstrated path to root

Specifically, the most severe vulnerability is in nginx HTTP/2 flow control. An unauthenticated remote attacker can corrupt memory in an nginx worker, leak memory addresses, and overwrite the pointer to a cleanup function that runs when a connection closes. This can be used to execute commands with worker privileges and receive the output over an existing connection.

The demonstrated entry point needs an externally reachable HTTP/2 port. From there,

the exploit corrupts the send window, leaks memory addresses, and executes commands with nginx worker privileges.

nginx HTTP/2 finding · remote, unauthenticatedReachable HTTP/2 port

Send window corrupted

Memory addresses leaked

Cleanup function pointer overwritten

Commands run as the nginx worker

Linux kernel · local privilege escalationSeparate Linux SCTP kernel vulnerability

Root on the host

nginx HTTP/2 finding · remote, unauthenticated Linux kernel · local privilege escalation

nginx hosts in the affected version range

The HTTP/2 vulnerability has existed since nginx introduced HTTP/2 in 2015. In a November 10, 2026 snapshot, 98.9% of hosts with identifiable nginx versions ran releases within the affected version range. That number describes version prevalence; it does not establish whether each host exposes HTTP/2 or has received a backported fix.

98.9%in range

Affected range11.8MOutside range0.14M

Version prevalence, not a count of exploitable endpoints. Source: Shodan

nginx share of websites

Attackers can fingerprint nginx with widely available tools and identify exposed deployments. W3Techs estimates that nginx is used by about 30% of websites whose web server it can identify.

about 30%

nginx Other web servers

Source: W3Techs

How Xint found NGINX2Root

nginx runs roughly a third of the web and has been fuzzed and audited by the best researchers in the world for two decades. Pre-auth RCE in nginx almost never happens. The best known one is from 2013. This year every AI lab pointed models at it. Everyone figured the easy bugs were long gone. While testing a new Xint capability ahead of ZeroDay Cloud, a Xint researcher pointed it at a slice of nginx, about 50,000 lines. He picked the target; Xint did the rest. Ninety minutes later it flagged high severity issues with reproduction steps specific enough to become a working exploit in under ten minutes.

The human researcher was the one that found the specific vuln that affects a default nginx setup with HTTP/2 enabled. This discovery was around the same time this same researcher 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. All five were found independently; one was also found by other researchers around the same time.

Impact

Why our findings matter

The impact depends on how widely the affected code is deployed and whether the attack works in realistic environments. We examined nginx version prevalence and validated the attack chain in controlled cloud environments.

The HTTP/2 code path dates to nginx 1.9.5 in 2015. In Xint’s November 10, 2026 Shodan snapshot, 11.8 million of 11.94 million version-identifiable nginx hosts ran releases in the affected range. That is a measure of version prevalence, not a count of exploitable endpoints. Xint also found that 88.6% of Fortune 500 companies use nginx.

Xint surfaced the initial flaw without human guidance, and its researchers followed it beyond a crash. The team validated the chain in controlled AWS, GCP, and Azure setups, including public HTTPS paths.

5 + 1Five nginx CVEs and one Linux kernel vulnerability, each with a proven exploit

88.6%of Fortune 500 companies use nginx (Source: Xint)

99%of 11.94M version-identifiable nginx hosts run an affected release

4 of 5found by Xint with no human guidance

Exposure

Who is affected?

The version range below applies to the HTTP/2 remote-code-execution finding, the most severe of the five. Official nginx releases from 1.9.5 through 1.31.8 contain the affected code. Exposure requires HTTP/2 support in the nginx build and an affected listener that accepts HTTP/2 connections.

Each of the other four CVEs is a distinct vulnerability with its own affected range and exploit. Check its individual advisory rather than applying the HTTP/2 finding’s version range to all five.

Distribution packages, appliances, and container images may backport a security fix while retaining an older version string. Confirm patch status from the relevant vendor advisory instead of relying on nginx -v⁠ alone. The host-root stage uses a separate Linux SCTP kernel vulnerability and must be assessed separately.

Quick check for the HTTP/2 finding

All five conditions must hold for a host to be exposed

  1. nginx version1.9.5 – 1.31.8
  2. HTTP/2 moduleCompiled into the build
  3. Active HTTP/2 listenerhttp2⁠ in the running config
  4. External h2 negotiationALPN check from outside
  5. Vendor patch statusAdvisory or changelog

Remediation

How do I fix it?

Apply the fixed nginx release or your vendor’s security update as soon as it is available. If you cannot update immediately, disable HTTP/2 on every affected nginx listener until the fix is applied. This mitigates the HTTP/2 finding; follow the separate advisories for the other four CVEs and the Linux kernel finding.

Apply the fix

Update to 1.31.9⁠ from nginx.org, or install your vendor’s security update. Restart nginx after updating. nginx -s reload⁠ does not load the new binary.

Can’t update right away? Disable HTTP/2

Temporary

  1. nginx 1.25.1 and later

listen 443 ssl; http2 off; nginx 1.9.5 through 1.25.0 · remove http2 from the affected listen directive

listen 443 ssl; 2. ### Test, reload, and verify from outside

Test the configuration and reload nginx. Then check from outside that the nginx endpoint no longer negotiates h2 and that HTTPS still serves the expected application.

Terminal

sudo nginx -t && sudo nginx -s reload openssl s_client -connect HOST -servername HOST -alpn h2 </dev/null 2>&1
| grep -F 'ALPN protocol: h2' A missing h2 result is meaningful only if the TLS connection itself succeeds. For packages with backported fixes, follow the vendor’s advisory and package update instructions.

Need help checking your whole fleet?

The team that found nginx2root can test your code and live applications.

Get in touch with Xint

Demo

See it in action

Technical details

Five findings. Five exploits.

One demonstrated path to root.

The sequence below describes the most severe HTTP/2 finding. The other four CVEs are distinct vulnerabilities with separate exploit analyses.

  1. Queue and refund nginx reserves connection send credit when response DATA enters its output queue. A connection-level WINDOW_UPDATE⁠ replenishes that credit while the DATA is still queued. Canceling the stream removes the unsent DATA and returns the reserved credit, pushing the counter above its maximum.

  2. Invalid window and memory access The next WINDOW_UPDATE⁠ check calculates the remaining window capacity using a value that already exceeds the limit. Differences in signed and unsigned interpretation cause the invalid window value to produce an incorrect copy length in the TLS output path. This leaks memory addresses and corrupts heap metadata.

  3. Worker code execution The attacker overwrites a connection cleanup function pointer with controlled data. When the connection closes, the function runs, executing commands with nginx worker privileges.

  4. Privilege escalation to host root In the tested chain, a separate Linux SCTP kernel vulnerability escalates privileges from the nginx worker account to root on the host.

Disclosure timeline

39 days from discovery to fix (KST)

  1. 2026 Oct 11Found
  2. 2026 Oct 16Reported to F5 via HackerOne
  3. 2026 Nov 19Fix released

References

FAQ

Frequently asked questions

About nginx2root

5 questions

What is nginx2root? nginx2root refers to five nginx vulnerabilities and a separate Linux kernel SCTP vulnerability discovered by Theori’s Xint research team. The nginx vulnerabilities affect a variety of configurations, and the Xint team demonstrated remote code execution using each vulnerability independently. Each nginx vulnerability can be chained with the Linux kernel vulnerability to obtain root privileges on the host.

What privileges can an attacker gain? The nginx vulnerabilities enable an attacker to execute arbitrary commands with nginx worker privileges. These privileges may also allow access to application data, secret credentials, or internal services. Using the full nginx2root vulnerability chain, an attacker can gain root privileges on the host and even escape containers. The nginx vulnerabilities and the kernel vulnerability must be patched separately.

How serious is it? Critical: the impact is unauthenticated remote code execution as root, and the vulnerabilities affect widely used configurations. For example, the default nginx configuration with HTTP/2 enabled is vulnerable. See “Checking exposure” below for more details about other vulnerable configurations.

Is it being exploited? We have no evidence of exploitation as of publication, but some of the bugs are over ten years old, so we cannot rule it out.

Will the exploit be published? Not yet. We are not publishing the exploit now because the risk is too high.

Checking exposure

8 questions

Which nginx configurations should I check? The five vulnerabilities affect different features. Check the installed build, its patch status, and the relevant configuration.

VulnerabilityConfiguration to check
CVE-2026-123007Servers with HTTP/2 enabled
CVE-2026-123634Servers using resolver⁠, proxy_pass⁠, mirror⁠, and mirror_request_body off⁠ together
CVE-2026-123633Servers using HTTP/2 and upstream connections through directives such as proxy_pass⁠, fastcgi_pass⁠, or grpc_pass⁠
CVE-2026-121810Servers using HTTP/3/QUIC and upstream connections through directives such as proxy_pass⁠, fastcgi_pass⁠, or grpc_pass⁠
CVE-2026-113425Mail proxy servers using proxy on⁠ and auth_http⁠

Affected version ranges and the full prerequisites differ by vulnerability. See Section 4 of the research report for details.

How do I check whether I am affected by CVE-2026-123007? Versions 1.9.5 through 1.31.8 are affected. Check whether your package includes the patch, whether the build supports HTTP/2 (nginx -V⁠), and the listener configuration (nginx -T⁠). Also verify that the running service is actually using that configuration. A server that supports HTTP/2 and lacks the security patch for this vulnerability may be vulnerable.

Can an older version number still indicate a patched package? Yes. Distributions may backport fixes without changing the upstream version number displayed by nginx -v⁠. Compare the full package version against your distribution’s security advisory for the relevant CVE.

Am I safe if I disable HTTP/2? Once HTTP/2 is disabled on every externally accessible nginx listener and all existing HTTP/2 connections have ended, CVE-2026-123007 and CVE-2026-123633 no longer apply to those listeners. Check the DNS resolver, HTTP/3, and mail proxy vulnerabilities separately.

What if nginx is only accessible from an internal network? Running a service only on an internal network limits who can reach it, but does not change the vulnerable code. Clients on the permitted network can still access the service, so it could be used by an attacker to move laterally through your network. Include internal servers in your patching and configuration review.

What changes if I run nginx in Docker or Kubernetes? The Xint team demonstrated remote code execution with root privileges on the host, even when nginx was running in a Docker container. Whether the same attack chain works in other environments depends on the host kernel’s security patch status.

Does a CDN or load balancer protect my nginx server? For the HTTP/2 vulnerabilities, a frontend that terminates HTTP/2 connections, forwards requests to nginx over HTTP/1.1, and blocks direct access to the nginx server can block this attack path. However, the server may remain vulnerable if TLS passthrough is used or if the connection to nginx still uses HTTP/2.

How do I check products that include nginx? Check the nginx build included in the product, its enabled features, and the vendor’s security advisories. Locate the product in your package and image inventories, and apply the appropriate vendor-provided updates.

Updates and mitigations

5 questions

What should I do first? Identify affected listeners and install an update containing the fixes if one is available. If you cannot patch immediately, disable HTTP/2 where your application permits it, then verify the configuration and the behavior of each endpoint. After the change, make sure existing HTTP/2 connections are no longer being processed. Review HTTP/3 and mail proxy settings separately.

Which release or package should I install?

Patched upstream nginx release: 1.31.9

For distribution packages, images, and appliances, consult the vendor’s security advisory to identify a build containing the fixes. The Linux kernel vulnerability requires a separate update. Follow your kernel vendor’s advisory for affected builds and remediation steps.

Is reloading the configuration enough after updating nginx? No. nginx -s reload⁠ reloads the configuration but does not replace the running binary. Use the restart, rolling replacement, or binary upgrade procedure appropriate for your deployment, and verify that all old processes have exited.

Will disabling HTTP/2 affect my application? Web clients can use HTTP/1.1 if the service supports it, but performance may suffer. Other clients, such as gRPC, require HTTP/2, so remote procedure calls may stop working. Test your clients before changing the configuration.

Can a web application firewall or connection limits replace patching? Web application firewall rules that inspect URLs or request bodies cannot eliminate vulnerabilities in HTTP/2 frame processing code. Use them alongside patches or configuration changes that prevent access to the vulnerable features.

Investigating a possible compromise

3 questions

What should I investigate? Look for unexpected command execution or child processes associated with nginx worker processes, repeated worker crashes, and unusual network activity. Repeated crashes or processes running under the nginx account alone do not prove exploitation, but may indicate a high likelihood of compromise.

Can ordinary access logs establish that no attack occurred? No. Ordinary access logs do not fully record HTTP/2 control frames used by the vulnerabilities, such as WINDOW_UPDATE⁠ and RST_STREAM⁠. Review error logs, process execution records, and network activity captures as well.

What should I do if I confirm a compromise? Isolate affected systems and preserve evidence according to your organization’s incident response procedures. Identify the files, credentials, and services the compromised process could access, and rotate exposed secrets. Investigate the possibility of host compromise as well. If host compromise is confirmed, recover using a trusted image. Patching alone does not remove changes an attacker has made to the system.

The kernel bug

1 question

Does patching nginx close the whole chain? It closes the way in through nginx. The kernel bug is a separate local privilege escalation vulnerability and needs its own patch, which will be released in the coming weeks.

Disclosure

3 questions

When was it reported and fixed? Found October 11, 2026. Reported to F5 through HackerOne on October 16. Fix released November 19 (KST). See the Xint blog guide for the full timeline.

Who found it? The Xint research team at Theori: Soomin Shin (imssm99), Joohyun Park (cdor1), Tim Becker (tjbecker), and Yves Bieri (yves.bieri).

Where can I find updates? This page and the Xint blog.