Five NGINX flaws allow unauthenticated remote code execution
On 18 November 2026, F5 released an advisory fixing five vulnerabilities in NGINX Open Source and NGINX Plus. The flaws let an unauthenticated attacker run code with the privileges of the worker process, and CERT-EU urges prompt updates, starting with internet-facing servers.
What to do now
- Product
- NGINX Open Source, NGINX Plus
- Affected versions
- NGINX OSS mainline 1.9.5 to 1.31.8 (varies by flaw), stable 1.30.x incl. 1.30.6; NGINX Plus 37.0.0–37.0.7.1, 37.1.0–37.2.0.1, R34 to R36
- CVE
- CVE-2026-123007
F5 published a security advisory on 18 November 2026 covering five vulnerabilities in NGINX, and CERT-EU relayed it the same day. An unauthenticated remote attacker can exploit any of the five. Each one can lead to code execution with the privileges of the NGINX worker process.
Researchers have demonstrated a working exploit for CVE-2026-123007. CERT-EU says no in-the-wild exploitation has been reported so far. The flaw is an integer overflow in HTTP/2 flow control that triggers an out-of-bounds heap write. Its only precondition is HTTP/2 being enabled on a listening port, which puts a large share of deployments in scope.
The remaining four are use-after-free bugs that depend on narrower configurations. CVE-2026-123633 occurs when connection draining closes an active HTTP/2 connection while NGINX is connecting to an upstream server. It requires HTTP/2 and upstream proxying. CVE-2026-121810 involves a QUIC connection drained during stream creation and upstream connection, and needs HTTP/3 with upstream proxying. CVE-2026-123634 sits in the DNS resolver waiting list. It requires a configured resolver, a proxy_pass destination built from request data, and mirror with mirror_request_body off. CVE-2026-113425 is triggered when a client drops the connection during an auth_http lookup on a mail proxy configured with proxy on.
The affected releases are NGINX Open Source mainline 1.9.5 through 1.31.8, with the exact range depending on the flaw. The stable 1.30.x branch is also affected, including 1.30.6. NGINX Plus is affected from 37.0.0 to 37.0.7.1 and from 37.1.0 to 37.2.0.1, along with R34, R35 and R36. CERT-EU does not list fixed versions and points readers to F5 advisory K000164058.
Where an immediate update is not possible, turning off HTTP/2 on exposed listeners mitigates CVE-2026-123007 and CVE-2026-123633. To do this, remove http2 from the listen directives or set http2 off;. This step does not address the other three flaws.
For detection, CERT-EU suggests watching the error log for worker crashes, which appear as "worker process … exited on signal". These entries point to exploitation attempts rather than confirmed code execution. Process creation logs should be reviewed as well to assess whether a system was compromised.
What to do now
- Update NGINX Open Source and NGINX Plus to the fixed releases listed in F5 advisory K000164058, starting with internet-facing instances.
- Until patched, disable HTTP/2 on exposed listeners (remove http2 from listen or set http2 off;) to mitigate CVE-2026-123007 and CVE-2026-123633.
- Check whether your configurations use HTTP/3, a resolver with request-derived proxy_pass and mirror, or a mail proxy with auth_http, to gauge exposure to the other flaws.
- Search error logs for "worker process … exited on signal" and review process creation logs for signs of compromise.