> ## Content Index
> Fetch the complete content index at: https://blog.previdian.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# NGINX2Shell (CVE-2026-123633 and CVE-2026-123007): What We Know So Far
- URL: https://blog.previdian.com/nginx2shell-cve-2026-123633-and-cve-2026-123007-what-we-know-so-far/
- Published: 2026-11-19T11:28:57.000Z
- Updated: 2026-11-19T12:38:13.000Z
- Author: Ryan Dewhurst
- Tags: FAQ

**Published:** 19 November 2026 | **Last Updated:** 19 November 2026, UTC

Two critical vulnerabilities in NGINX's HTTP/2 implementation could allow unauthenticated attackers to execute code on affected servers.

Tracked as **CVE-2026-123633 and CVE-2026-123007**, the vulnerabilities were independently discovered by Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint. F5 coordinated their disclosure on 18 November 2026 and released security updates.

Both require HTTP/2 to be enabled, but their exploitation conditions differ.

## At a Glance

|                         |                                                                         |
| ----------------------- | ----------------------------------------------------------------------- |
| **CVE**                 | CVE-2026-123633, CVE-2026-123007                                        |
| **Affected Product**    | NGINX Open Source and NGINX Plus                                        |
| **Severity**            | Critical, 9.2 (CVSS v4.0), both vulnerabilities                         |
| **Exploitation Status** | No confirmed in-the-wild exploitation identified as of 19 November 2026 |
| **Public Exploit**      | Lab-specific RCE PoC published for CVE-2026-123007                      |
| **Patch Available**     | Yes, released 18 November 2026                                          |

## What Is NGINX2Shell?

NGINX2Shell refers to two memory-safety vulnerabilities affecting NGINX's HTTP/2 implementation.

**CVE-2026-123633: HTTP/2 Use-After-Free**

A connection can be freed while NGINX is still processing a request. Exploitation requires HTTP/2, upstream proxying, and conditions where available worker connections run low.

**CVE-2026-123007: HTTP/2 Flow-Control Underflow**

An integer underflow in HTTP/2 flow-control accounting can cause an out-of-bounds memory operation.

Unlike CVE-2026-123633, this vulnerability does not require a reverse-proxy configuration. Wiz demonstrated remote code execution against NGINX serving ordinary static files.

Both vulnerabilities can potentially allow unauthenticated code execution with the privileges of the NGINX worker process. Researchers demonstrated bypasses of Address Space Layout Randomization (ASLR) in laboratory environments.

## Who Is Affected?

Both vulnerabilities affect NGINX installations with HTTP/2 enabled, provided their individual exploitation conditions are met.

| CVE             | NGINX Open Source Affected Versions             | Additional Conditions                                |
| --------------- | ----------------------------------------------- | ---------------------------------------------------- |
| CVE-2026-123633 | 1.19.7 through vulnerable releases up to 1.31.8 | HTTP/2 proxying and low available worker connections |
| CVE-2026-123007 | 1.9.5 through vulnerable releases up to 1.31.8  | HTTP/2 enabled; no backend application required      |

NGINX Plus is also affected. Its fixed-release requirements differ between the vulnerabilities and release tracks.

The fixed NGINX Open Source versions are **1.30.7 (stable)** and **1.31.9 (mainline)**.

## Is NGINX2Shell Being Exploited in the Wild?

As of 19 November 2026, we have not identified independently confirmed reports of in-the-wild exploitation in the sources reviewed.

At the time of its 18 November publication, Previdian had not observed attempted exploitation of either vulnerability across its honeypot network.

However, public exploit research is available.

- **CVE-2026-123007:** Rapid7 published a working RCE proof of concept demonstrated against a vulnerable NGINX Docker environment. The published approach has substantial bandwidth, hardware, and environmental requirements.
- **CVE-2026-123633:** Researchers demonstrated RCE in laboratory settings. Public crash reproductions have also appeared, but a general-purpose public RCE exploit has not been independently verified.

A published PoC does not establish active exploitation against production systems.

## Is a Patch or Mitigation Available?

Yes. Fixed versions are available for both NGINX Open Source and NGINX Plus.

| Product                       | Fixed Release Covering Both CVEs |
| ----------------------------- | -------------------------------- |
| NGINX Open Source stable      | 1.30.7                           |
| NGINX Open Source mainline    | 1.31.9                           |
| NGINX Plus LTS                | 37.0.8.1                         |
| NGINX Plus Continuous Release | 37.3.0.1                         |

NGINX Plus has different minimum fixed releases for each CVE. The versions above address both.

If immediate patching is not possible, temporarily disable HTTP/2 on affected listeners. For NGINX 1.25.1 and later, use `http2 off;`. For earlier versions, remove `http2` from the `listen` directive.

Disabling HTTP/2 mitigates these two vulnerabilities but does not address other NGINX issues disclosed at the same time.

## What Should Defenders Do?

1. **Identify exposed installations.** Inventory NGINX versions and determine where HTTP/2 is enabled.
2. **Apply security updates.** Upgrade to a fixed release and restart NGINX to ensure the updated binary is running.
3. **Disable HTTP/2 if necessary.** Use this temporary mitigation until patching is completed.
4. **Investigate suspicious activity.** Review unexpected worker crashes, abnormal process execution, and unusually long-lived or high-volume HTTP/2 connections where telemetry is available.
5. **Verify upstream exposure.** CDNs and WAFs that terminate HTTP/2 may reduce exploitability, but protection depends on their configuration and behavior.

Worker crashes and anomalous traffic are not, by themselves, confirmation of exploitation.

## What Remains Unknown?

The prevalence of real-world exploitation, the reliability of public exploits against varied production configurations, and whether attackers have developed additional exploitation techniques remain uncertain.

## Updates

- **19 November 2026, UTC:** Initial publication covering the 18 November disclosure, fixed versions, exploitation prerequisites, and publicly available research.

## References

- [NGINX2Shell: Vulnerability Overview](https://nginx2shell.com/?ref=blog.previdian.com)
- [NGINX Security Advisories](https://nginx.org/en/security%5Fadvisories.html?ref=blog.previdian.com)
- [NGINX Plus Release Notes](https://docs.nginx.com/nginx/releases/?ref=blog.previdian.com)
- [Wiz Research: Unauthenticated RCE in NGINX](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities?ref=blog.previdian.com)
- [Rapid7: CVE-2026-123007 Technical Analysis](https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/?ref=blog.previdian.com)
- [CERT-EU: Critical Vulnerabilities in NGINX](https://cert.europa.eu/publications/security-advisories/2026-022?ref=blog.previdian.com)