F5 NGINX: five unauthenticated RCE flaws, public PoC
F5 fixes five NGINX flaws (CVSS 8.1) allowing unauthenticated RCE via HTTP/2, HTTP/3, the resolver and mail proxy. Versions, mitigations and checks.

On 18 November 2026 F5 published fixes for five NGINX vulnerabilities that, according to the CERT-EU advisory, allow a remote unauthenticated attacker to execute code with the privileges of the NGINX worker process. All five have a CVSS score of 8.1. CERT-FR issued an alert bulletin (CERTFR-2026-ALE-017) for the two HTTP/2-related flaws, CVE-2026-123007 and CVE-2026-123633, and states that it is aware of a public proof of concept (PoC) for CVE-2026-123007.
CERT-EU notes that researchers have demonstrated exploitation of CVE-2026-123007, but that no exploitation in the wild has been reported so far. Both agencies recommend updating as soon as possible, starting with internet-facing servers.
The five vulnerabilities
According to CERT-EU, each one requires a specific configuration condition:
- CVE-2026-123007: integer overflow in HTTP/2 flow control causing an out-of-bounds heap write. The only precondition is HTTP/2 enabled on a listening port: it is the broadest of the five.
- CVE-2026-123633: use-after-free when connection draining closes an active HTTP/2 connection while NGINX is connecting to an upstream server. It requires HTTP/2 enabled and requests forwarded to an upstream.
- CVE-2026-121810: use-after-free when a QUIC connection is drained during stream creation and upstream connection. It requires HTTP/3 enabled and requests forwarded to an upstream.
- CVE-2026-123634: use-after-free in the processing of the DNS resolver waiting list. It requires a configured
resolver, aproxy_passdestination built from request data andmirrorwithmirror_request_body off. - CVE-2026-113425: use-after-free when the client closes the connection during the
auth_httpauthentication lookup. It affects the mail proxy configured withproxy onandauth_http.
In MITRE ATT&CK terms, exploitation falls under T1190 (Exploit Public-Facing Application).
Affected and fixed versions
- NGINX Open Source: according to CERT-FR, versions 1.31.x before 1.31.9 and versions before 1.30.7 are vulnerable. CERT-EU lists the mainline branch from 1.9.5 to 1.31.8 (the range depends on the flaw) and the stable 1.30.x branch, including 1.30.6.
- NGINX Plus: CERT-EU lists versions 37.0.0 to 37.0.7.1 and 37.1.0 to 37.2.0.1 as affected, as well as R34, R35 and R36. The NGINX Plus versions reported by CERT-FR do not fully match these: for fixed versions, the F5 bulletin is authoritative (K000164058, and K000163926 and K000163928 for the two HTTP/2 flaws).
Advisory CERTFR-2026-AVI-1567, based on F5’s bulletin of the same day, also lists BIG-IP (branches 17.1, 17.5 and 21.1), BIG-IQ Centralized Management 8.4 and BIG-IP Next for Kubernetes 2.2, 2.3 and 2.4, with risks of remote code execution, denial of service and security policy bypass: if you use these products, check the fixed builds in the same bulletin.
Impact for European and Italian companies
NGINX is widely used as a web server, reverse proxy and load balancer in front of applications and APIs, often right on the internet-facing perimeter. CVE-2026-123007 only requires HTTP/2 enabled and already has a public PoC: it is the first one to check.
For NIS2 entities, this falls under vulnerability management with documented priorities and timelines; any significant incident must be assessed for notification to the national CSIRT (in Italy, CSIRT Italia at ACN). In healthcare, NGINX often publishes patient portals and APIs of clinical applications: include them in the inventory.
What to do now
- Take inventory of where NGINX runs, including container images and appliances.
nginx -Vshows the version and compiled modules,nginx -Tthe effective configuration. - Update NGINX Open Source to 1.31.9 or 1.30.7, and NGINX Plus to the versions indicated by F5, starting with internet-facing servers, as CERT-EU and CERT-FR recommend.
- If you cannot update right away, disable HTTP/2 on exposed listeners: according to CERT-EU, by removing
http2from thelistendirectives or by settinghttp2 off;. This mitigates only CVE-2026-123007 and CVE-2026-123633. After the change, CERT-FR suggests testing and reloading the configuration withnginx -t && nginx -s reloadand checking withopenssl s_client -alpn h2that the server no longer negotiates theh2protocol. - Check the conditions of the other three flaws in your configuration: HTTP/3 with forwarding to an upstream (CVE-2026-121810),
resolverwithproxy_passbuilt from request data andmirrorwithmirror_request_body off(CVE-2026-123634), mail proxy withproxy onandauth_http(CVE-2026-113425). The advisories give no workarounds for these: updating is the remedy. - Look for exploitation attempts: according to CERT-EU, worker crashes («worker process … exited on signal» lines in the error log) indicate possible attempts, but are not a reliable sign of successful code execution. CERT-EU recommends also checking process creation logs.
How ARXDOME helps
The ARX Sentry inventory lists the software, processes and ports of every server running the agent, so you can find where NGINX runs. ARX Shield shows open vulnerabilities by machine and by package, ARX Expose which of your company’s public services have known vulnerabilities: together they help you decide which servers to start with.
Last updated:


