English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

NGINX: two HTTP/2 flaws allow unauthenticated remote code execution

On 18 November 2026, F5 published two advisories covering CVE-2026-123633 and CVE-2026-123007, which allow remote code execution on NGINX Open Source and NGINX Plus over HTTP/2. CERT-FR reports a public proof of concept for one of them, putting any organisation running an internet-facing NGINX server with HTTP/2 enabled at risk.

What to do now Illustration photo (data center)
CVSS severity9.2Critical
EPSS probability6 %
ExploitationNot observed
PatchAvailable
Product
F5 NGINX Open Source and NGINX Plus
Affected versions
NGINX Open Source 1.31.x < 1.31.9 and < 1.30.7; NGINX Plus 3.1.x to 3.2.x < 3.7.3.0.1 and 3.7.x < 37.0.8.1
Fixed in
NGINX Open Source 1.31.9 and 1.30.7; NGINX Plus 3.7.3.0.1 and 37.0.8.1, depending on branch
CVE
CVE-2026-123007

France's CERT-FR issued an alert on 18 November 2026 (CERTFR-2026-ALE-017) about two NGINX vulnerabilities tracked as CVE-2026-123633 and CVE-2026-123007. The alert follows two security bulletins released the same day by F5, the vendor, under references K000163926 and K000163928.

Both the free NGINX Open Source and the commercial NGINX Plus are affected. According to CERT-FR, an unauthenticated remote attacker can exploit the flaws through the HTTP/2 protocol to run arbitrary code. Any NGINX web server, reverse proxy or load balancer reachable with HTTP/2 enabled should be considered potentially exposed.

CERT-FR says it is aware of a public proof of concept for CVE-2026-123007, which raises the urgency. The alert does not state whether active exploitation has been observed.

The bulletin lists the following affected versions: NGINX Open Source 1.31.x before 1.31.9, NGINX Open Source before 1.30.7, NGINX Plus 3.1.x through 3.2.x before 3.7.3.0.1, and NGINX Plus 3.7.x before 37.0.8.1. CERT-FR points administrators to F5's bulletins to obtain the fixes.

Until patches are in place, CERT-FR recommends turning off HTTP/2. How to do this depends on the NGINX version: either remove HTTP/2 support from the relevant listen directives or use the "http2 off;" directive, following the guidance quoted in the alert. The configuration should then be checked with "nginx -t" and reloaded. An openssl s_client connection requesting the h2 ALPN protocol confirms whether the server still negotiates HTTP/2.

Action plan

What to do now

  1. Apply the F5 fixes described in bulletins K000163926 and K000163928, moving to at least NGINX Open Source 1.31.9 or 1.30.7 and NGINX Plus 3.7.3.0.1 or 37.0.8.1 depending on your branch.
  2. Inventory every NGINX Open Source and NGINX Plus instance, including reverse proxies and load balancers, and identify those with HTTP/2 enabled.
  3. If you cannot update immediately, disable HTTP/2 in the configuration, validate it with "sudo nginx -t" and reload with "sudo nginx -s reload".
  4. Confirm with "openssl s_client -connect HOST:443 -servername HOST -alpn h2" that the output no longer shows "ALPN protocol: h2".
  5. As general good practice, review logs and behaviour of exposed NGINX servers for unusual activity, given that a proof of concept is public.

Sources