NGINX Plus and Open Source use-after-free RCE

Critical 9.2 CVE-2026-123634

High risk · public exploit

Severity 9.2 Reach 10.0 Ease 3.0 Exploitation 2.0 Tooling 5.0

Risk assessment

NGINX Plus and NGINX Open Source use-after-free in proxy, SSI, and mirror configurations can crash workers or enable RCE (CVSS 9.2). Update 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-123634 is a critical use-after-free in NGINX Plus and NGINX Open Source that can crash worker processes, corrupt memory, or grant remote code execution when NGINX runs as a proxy with variable server names and SSI or mirror subrequests. F5 has patched the issue; upgrade to the fixed release immediately.

Overview

CVE-2026-123634 is a use-after-free vulnerability that appears when NGINX is configured in a specific but realistic way. Three conditions must line up: NGINX acts as a proxy, the proxied server name contains variables, and a Server Side Includes (SSI) directive or a mirror directive sends a subrequest to a location that resolves the same server name.

When all three are present, a specially crafted HTTP request can trigger the use-after-free inside a worker process. Memory the worker believed was still allocated gets reused, and the worker can crash, return corrupted data, or hand an attacker primitive control over memory. The CVSS score is 9.2 (CRITICAL) with an attack vector of NETWORK, high attack complexity, and no privileges or user interaction required. The high complexity reflects the configuration prerequisites rather than a barrier to a determined attacker: once a target is fingerprinted, crafting the request is straightforward.

Impact

The direct consequences are worker crashes (denial of service) and memory corruption. The serious consequence is remote code execution. Code execution requires either ASLR to be disabled or the attacker to bypass it, which raises the practical bar but does not eliminate the risk on hardened or legacy hosts. Shared and edge deployments are the most exposed: a crash takes down every request routed through that worker, and a memory-corruption success means code running with the worker’s privileges.

CISA KEV lists this vulnerability as not confirmed to be actively exploited. EPSS estimates a 1.6% probability of exploitation in the next 30 days. Treat it as a credible risk rather than a confirmed campaign.

Remediation and mitigations

  • Upgrade NGINX Plus and NGINX Open Source to the fixed release listed in the F5 advisory for CVE-2026-123634. Older versions that have reached End of Technical Support are not evaluated and should be retired.
  • Audit proxy_pass and related directives for variable server names combined with SSI or mirror. Remove variable expansion or the subrequest path where it is not required.
  • If you cannot patch immediately, disable SSI (ssi off) and mirror directives on affected server blocks, or isolate the upstream name so the subrequest cannot resolve the same server.
  • Restrict exposure of admin and health endpoints, and rate-limit requests that reach the vulnerable location.
  • Keep ASLR enabled at the OS level. It does not fix the bug but removes the easiest path to code execution.
  • Monitor worker crash and segfault logs for unusual spikes after deploying a change.

Security Insight

This is a textbook example of emergent memory-safety risk: each NGINX feature (proxy variables, SSI, mirror) is individually safe, but their combination creates a lifetime bug that unit testing rarely catches. C memory management in a global traffic-managing proxy means every such flaw carries deny and execute risk simultaneously, which is precisely the class that commodity scanners miss until a proof-of-concept surfaces. Watch security news for exploitation telemetry, and check breach reports if a crash coincides with suspicious activity on an exposed host.

Further Reading

Exploit references 1 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
LLCForge/CVE-2026-123634

CVE-2026-123634 — nginx resolver use-after-free via SSI subrequests. Self-contained Docker lab with a delayed DNS responder, crash detector, and vulnerable/fixed version comparison.

★ 0

Showing 1 of 1 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.