Five critical NGINX flaws allow unauthenticated remote code execution
F5 fixed the issues in NGINX Open Source 1.30.7 and 1.31.9; Xint cites proven exploits but no confirmed attacks.
Use-after-free in NGINX with variable proxy server names
A use-after-free in an NGINX worker can occur when NGINX Plus or NGINX Open Source proxies to a server name that includes variables, and an SSI or mirror directive sends a subrequest that resolves the same name. A remote, unauthenticated attacker can trigger it with a crafted HTTP request, crashing the worker, corrupting memory, or running code if ASLR is off or bypassed. Affected builds are not listed.
What to do: F5 has not listed a fixed version for CVE-2026-123634, and no workaround is stated.
| Product | Affected |
|---|---|
| F5 NGINX Plus | — |
| F5 NGINX Open Source | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
F5 fixed the issues in NGINX Open Source 1.30.7 and 1.31.9; Xint cites proven exploits but no confirmed attacks.
Xint says HTTP/2 CVE-2026-123007 hits every release from 1.9.5 through 1.31.8, with 1.31.9 not yet available.
Researchers demonstrated CVE-2026-123007; CERT-EU reports no in-the-wild exploitation and urges internet-facing updates first.
The page lists five CVE IDs and links a fix guide, but gives no versions or exploitation status.
Today 2.2K readers · 2.4K views · 127 reads · all time 206K views