NGINX HTTP/2 use-after-free enables RCE

Critical 9.2 CVE-2026-123633

High risk · public exploit

Severity 9.2 Reach 10.0 Ease 3.0 Exploitation 2.0 Tooling 8.0

Risk assessment

NGINX HTTP/2 use-after-free lets remote attackers crash workers or execute code when ASLR is bypassed (CVSS 9.2). Patch to the latest release now.

By Yazoul AI · automated

What to do

Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.

Exploitation confirmed - public proof-of-concept - CVE-2026-123633 is a critical use-after-free in NGINX Plus and NGINX Open Source configured for HTTP/2 client connections with proxying to a backend, allowing remote attackers to crash worker processes or execute code when ASLR is disabled or bypassed. A crafted request triggers the flaw when the worker is low on worker_connections.

Overview

NGINX is a widely deployed web server and reverse proxy. When it accepts HTTP/2 connections from clients and forwards those requests to an upstream backend, a specially crafted request can trigger a use-after-free in the worker process. The condition surfaces when that worker is running low on worker_connections, meaning the bug is most reachable on busy servers under connection pressure.

A use-after-free means the worker frees memory and then keeps using it. On HTTP/2 the attacker controls request timing and multiplexing, so they can shape when that memory is released and reused. This is a data plane issue only: there is no control plane exposure.

Impact

The practical outcome depends on the target:

  • Denial of service. A single crafted request can crash the affected worker, dropping in-flight connections and degrading service. Repeated requests can keep pressure on the server.
  • Code execution. On systems with Address Space Layout Randomization (ASLR) disabled, or where an attacker can bypass ASLR, the same flaw can be turned into arbitrary code execution in the worker’s context.

CVSS scores this 9.2 (network attack vector, no privileges, no user interaction, high attack complexity). The EPSS score of 6.5% suggests some exploitation activity is plausible in the next 30 days, though this is not a confirmed actively exploited issue. Software versions that have reached End of Technical Support are not evaluated and should be treated as affected.

Remediation and Mitigation

  1. Patch. Update NGINX Plus and NGINX Open Source to a release containing the fix from the vendor advisory. Confirm the exact patched version in the NGINX security bulletin before rolling out.
  2. Interim workaround. Where you cannot patch immediately, disable HTTP/2 for client-facing server blocks or remove proxying of HTTP/2 client requests, so the vulnerable path is not reachable.
  3. Keep ASLR enabled. Do not disable ASLR on hosts running NGINX; it is a meaningful barrier against the code execution path here.
  4. Tune connection limits. Raising worker_connections and monitoring worker saturation reduces the window in which the use-after-free condition is reachable.
  5. Retire EoTS versions. Treat unsupported releases as vulnerable regardless of build date.

For related incident coverage, see our security news and breach reports.

Security Insight

NGINX has a strong track record, which makes a memory-safety bug on the HTTP/2 data path notable. It reflects the same pattern seen in HTTP/2 stacks across the industry - protocol complexity in connection and stream teardown creates lifecycle bugs that are hard to fuzz. The ASLR dependency in the code execution path is cold comfort: a DoS on the front door of most production estates is enough on its own.

Further Reading

Exploit references 3 PoC Show

Public PoC References

Unverified third-party code

These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).

Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.

Repository Stars
Ghost-Bx1/nginx-exploits

Exploits e PoCs para vulnerabilidades no NGINX - CVE-2026-123633, CVE-2026-123007

★ 11
LLCForge/CVE-2026-123633

CVE-2026-123633 — nginx HTTP/2 use-after-free under connection exhaustion (RST_STREAM race). CVSS 8.1. Affects nginx 1.19.7–1.31.8. Docker PoC.

★ 0
0xsaju/nginx-exploits

Exploits e PoCs para vulnerabilidades no NGINX - CVE-2026-123633, CVE-2026-123007

★ 0

Showing 3 of 3 known references. Source: nomi-sec/PoC-in-GitHub.

Share

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.