# NGINX2Root (CVE-2026-123007): Is Your NGINX Server Exposed?

Check whether NGINX is exposed to CVE-2026-123007, find fixed versions for your deployment, and verify your HTTP/2 mitigation.

Canonical URL: https://aiidelist.com/blog/nginx2root-cve-2026-123007-nginx-http2-vulnerability

Language: en

Published: 2026-11-19

Updated: 2026-11-19

## Key Takeaways

- **CVE-2026-123007 can allow remote code execution without a login** when a reachable NGINX listener accepts HTTP/2 and runs an affected build. Static sites, reverse proxies, and ingress controllers can all be exposed. [F5 security advisory](https://my.f5.com/manage/s/article/K000163926)
- **Upgrade upstream NGINX to 1.30.7 stable, 1.31.9 mainline, or a later patched release.** These releases also fix CVE-2026-123633, a separate HTTP/2 vulnerability. Linux distributions and managed products may ship the fixes under different version numbers. [NGINX security advisories](https://nginx.org/en/security_advisories.html)
- **If patching must wait, disable HTTP/2 on affected NGINX listeners and verify that existing HTTP/2 sessions have drained.** Check the origin and any internal listeners, including those behind a CDN or load balancer. [CERT-EU advisory](https://cert.europa.eu/publications/security-advisories/2026-022)

## What Is CVE-2026-123007?

CVE-2026-123007 is a memory corruption vulnerability in the NGINX HTTP/2 module. The affected code first shipped in NGINX 1.9.5 on September 22, 2015. The NGINX project released fixes on November 18, 2026. F5 rates the vulnerability **9.2 Critical under CVSS 4.0** and **8.1 High under CVSS 3.1**. Those scores use different versions of the scoring standard. [2015 NGINX release archive](https://nginx.org/2015.html) · [2026 release announcement](https://nginx.org/2026.html) · [F5 advisory](https://my.f5.com/manage/s/article/K000163926)

HTTP/2 flow control limits how much data can be sent before the receiving side grants more capacity. The flaw can cause NGINX to handle that limit incorrectly and write beyond an allocated memory buffer. A worker can crash, and successful code execution runs with the worker's privileges. Researchers demonstrated code execution with address space layout randomization, or ASLR, enabled. In a separate demonstration, they combined the NGINX compromise with a Linux kernel flaw to reach host root. **Review NGINX and host kernel exposure as separate patching tasks.** [CIRCL technical report](https://new.circl.lu/pub/tr-105/)

The HTTP/2 parser runs before the application handles the request. A WordPress login, a static site, or the absence of a backend therefore does not remove exposure to CVE-2026-123007. The published proof of concept demonstrates remote code execution under research conditions. Incident responders still need deployment-specific evidence to determine whether a server was compromised. [F5 advisory](https://my.f5.com/manage/s/article/K000163926) · [CIRCL technical report](https://new.circl.lu/pub/tr-105/)

## Affected Versions and Fixes

| Product | First fixed versions | What to verify |
| --- | --- | --- |
| NGINX Open Source | `1.30.7` stable or `1.31.9` mainline | Upstream `1.9.5` through `1.30.6` and `1.31.0` through `1.31.8` are affected when HTTP/2 is enabled. [NGINX advisories](https://nginx.org/en/security_advisories.html) |
| NGINX Plus | `37.0.8.1` or `37.3.0.1`, depending on the release line | F5 lists these as the fixes for CVE-2026-123007. Check the product bulletin for the maintenance line in use. [F5 advisory](https://my.f5.com/manage/s/article/K000163926) |
| Ubuntu 24.04 LTS packages | `1.24.0-2ubuntu7.20` | Canonical backported fixes for both HTTP/2 CVEs. Compare the full package revision with the Ubuntu notice. [USN-9159-1](https://ubuntu.com/security/notices/USN-9159-1) |
| Debian packages | Varies by Debian release and repository | Check the fixed package revision for the installed release. [Debian security tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007) |

**Check the package or image that supplied the running binary.** On Ubuntu 24.04 LTS, `nginx -v` can still show `1.24.0` after the security update. The distribution package revision records the backported fix. For a container, check what the running pod actually uses and confirm that every replica has rolled to the corrected image. For a hosting appliance or control panel, use its vendor's advisory for the bundled NGINX build. [Canonical update instructions](https://ubuntu.com/security/notices/USN-9159-1) · [Red Hat product bulletin](https://access.redhat.com/security/vulnerabilities/RHSB-2026-019)

## How to Check Whether Your Deployment Is Exposed

Start on the host or inside the container that runs NGINX. Use the same binary and configuration path as the service. The commands below show the build options and the configuration files NGINX would load. Review the configuration output privately because it can contain sensitive values. [NGINX command-line reference](https://nginx.org/en/docs/switches.html)

```bash
nginx -V
sudo nginx -T
```

Look for `http2 on` and the older `http2` option on `listen` directives. Review included files, inherited settings, and the default virtual host on each relevant address and port. A build with the HTTP/2 module becomes exposed to this flaw when an affected listener actually accepts HTTP/2 and is reachable by an untrusted client. [NGINX HTTP/2 documentation](https://nginx.org/en/docs/http/ngx_http_v2_module.html) · [F5 advisory](https://my.f5.com/manage/s/article/K000163926)

| Deployment | Where to check |
| --- | --- |
| NGINX terminates TLS on a public server | Inspect the public listener, its default virtual host, and any alternate ports. Static-only sites belong in this inventory. |
| A CDN or load balancer terminates TLS | Check the edge-to-origin protocol separately. Verify whether clients can also reach the origin directly. With TLS passthrough, check the NGINX listener that terminates TLS. |
| NGINX runs in Kubernetes | Check the controller, running image, and listener configuration. Include internal gateways that accept traffic from untrusted workloads. |

Cloudflare, for example, enables **HTTP/2 to Origin** by default. Browser DevTools shows the browser's connection to the edge. To check the next hop, use origin-side telemetry or review the CDN origin settings alongside the NGINX configuration. A separately established CDN connection and a direct client connection have different trust boundaries. [Cloudflare HTTP/2 to Origin documentation](https://developers.cloudflare.com/speed/optimization/protocol/http2-to-origin/)

To verify HTTPS protocol negotiation on an authorized listener, send a normal request with an HTTP/2-capable curl build. Replace the example hostname with the endpoint being checked. A result of `2` confirms HTTP/2 on that connection. A result of `1.1` verifies the fallback for that connection, so repeat the check for other listeners as applicable. Use configuration and package evidence to determine vulnerability status. [curl manual](https://curl.se/docs/manpage.html)

```bash
curl --http2 --silent --show-error --output /dev/null --write-out '%{http_version}\n' https://origin.example.com/
```

## How to Patch or Mitigate NGINX2Root

1. **Identify the package owner and install its fixed build.** Prioritize public NGINX listeners that accept HTTP/2. For managed ingress or hosting products, follow the bulletin for that product and release line.
2. **Roll the update through every instance.** Validate the configuration and use the service restart, container rollout, or documented executable upgrade procedure for the deployment. A configuration reload can leave the original executable running. Verify the new process or image after rollout. [NGINX process and upgrade documentation](https://nginx.org/en/docs/control.html)
3. **If a patch cannot be applied immediately, disable HTTP/2 on affected listeners.** Use `http2 off` where the directive is supported. On older configurations, remove the `http2` parameter from the relevant `listen` directives. Validate and reload, verify protocol negotiation, and confirm that existing HTTP/2 connections have drained. Test HTTP/2-dependent traffic such as gRPC before rollout. [CERT-EU mitigation guidance](https://cert.europa.eu/publications/security-advisories/2026-022) · [NGINX reload behavior](https://nginx.org/en/docs/control.html)
4. **Check related vulnerabilities before closing the ticket.** CVE-2026-123633 affects HTTP/2 reverse proxying under worker connection pressure. The same NGINX release also fixes separate issues in HTTP/3, the DNS resolver, and the mail proxy. Disabling HTTP/2 addresses the two HTTP/2 paths while those other features require their own review. [F5 advisory for CVE-2026-123633](https://my.f5.com/manage/s/article/K000163928) · [NGINX release announcement](https://nginx.org/2026.html)

For Kubernetes, **F5 NGINX Ingress Controller and the community `ingress-nginx` controller have separate release histories**. Kubernetes retired its community controller on March 24, 2026, and stopped issuing security updates. If the running controller is the retired project, verify the deployed image's status and plan a migration to a maintained controller or Gateway API implementation. [Kubernetes retirement notice](https://kubernetes.io/blog/2026/03/30/kubernetes-v1-36-sneak-peek/) · [F5 product advisory](https://my.f5.com/manage/s/article/K000163928)

## What to Review if an Exposed Server Was Unpatched

Correlate worker crashes or core dumps with unexpected child processes, unusual outbound connections or DNS activity, and long HTTP/2 sessions with large volumes of incoming traffic but few logged requests. An isolated crash has several possible causes. Ordinary access logs can also miss HTTP/2 control traffic, so review process and network telemetry alongside the logs. [CIRCL detection guidance](https://new.circl.lu/pub/tr-105/)

If the evidence suggests compromise, preserve relevant logs and process evidence and start incident response. Establish what the NGINX worker could access, including mounted files, credentials, and internal services. Check the host separately where the deployment could have allowed privilege escalation. [CIRCL incident handling guidance](https://new.circl.lu/pub/tr-105/)

## Conclusion

Inventory every NGINX instance that accepts HTTP/2 and patch the exposed ones first. For each instance, record the fixed package revision or image, verify that the patched process is running, and confirm that every replica has rolled over. If patching has to wait, verify that HTTP/2 is disabled on the affected listeners and set a deadline to install the permanent fix.
