Skip to content
Annuaire
Sections
Cybersecurity

NGINX: two HTTP/2 flaws allow remote code execution — what to do

L’essentiel

Two NGINX HTTP/2 flaws allow remote code execution. Versions to install, a workaround and signs of attack to watch for.

À retenir

Two NGINX HTTP/2 flaws allow remote code execution. Versions to install, a workaround and signs of attack to watch for.

On 18 November 2026, F5 released patches for two NGINX flaws related to the HTTP/2 protocol, CVE-2026-123007 and CVE-2026-123633, which can allow an attacker without credentials to execute code on the server. CERT-FR issued an alert the same day and reports a public proof of concept for one of them. The versions to install are 1.30.7 and 1.31.9; failing that, turning off HTTP/2 limits the risk.

Two old flaws in the HTTP/2 core

NGINX serves as a web server, load balancer or reverse proxy in front of a large share of online applications. Wiz, one of the teams involved in the coordinated disclosure with F5, notes, citing Netcraft’s September 2026 survey, that it powers more than 225 million sites. A flaw in its handling of HTTP/2 therefore concerns a considerable number of installations, from brochure websites to corporate API gateways.

According to Wiz’s technical analysis, the first flaw, CVE-2026-123007, stems from an underflow of a flow-control counter: when a cancelled stream returns its send window, the value can exceed the maximum allowed by the protocol, which eventually causes an out-of-bounds memory copy. The defect dates back to 2015 and affects versions 1.9.5 to 1.31.8. The second, CVE-2026-123633, is a use-after-free: an HTTP/2 connection still registered as reusable while a request has just started on it can be closed mid-request when free connection slots run out, and the memory still used by that request is then freed. It affects versions 1.19.7 to 1.31.8, and mainly reverse proxy configurations.

Wiz rates both defects as critical, with a score of 9.2 out of 10 on the CVSS 4.0 scale. nginx.org’s security advisories page assigns a “major” severity to the first and “medium” to the second. This difference in assessment does not change the instruction: both patches must be applied.

What the CERT-FR alert says

In its alert CERTFR-2026-ALE-017, the French agency reports that a proof of concept is circulating publicly for CVE-2026-123007. The affected products are NGINX Open Source before 1.30.7, the 1.31 branch before 1.31.9, and several versions of NGINX Plus, the commercial edition, for which it refers to F5 bulletins K000163926 and K000163928. Armees.com specifies that the bulletin reports no confirmed intrusion at this stage.

Wiz says it built exploits in the lab, which it will not publish, and achieved code execution with CVE-2026-123007 on the official 1.31.7 and 1.31.8 builds, bypassing address space layout randomization (ASLR), because the attacker can first read memory. A worrying point: for CVE-2026-123007, the demonstration was carried out on a 64-bit server that merely served static files over HTTPS, with no application or third-party module behind it.

The timeline also shows a race: Wiz says it reported CVE-2026-123633 to F5 on 21 October, with the vendor replying that another team had already done so. Wiz submitted CVE-2026-123007 on 16 November; F5 confirmed on the 17th that it was an already known defect, scheduled for the release of the 18th. Both defects were found independently by several teams, including Wiz, Rapid7, Ikotas Labs, Metnir and Xint.

Update, or turn off HTTP/2 in the meantime

The reference measure is to upgrade to NGINX 1.30.7 (stable branch) or 1.31.9 (mainline branch). The same versions fix eight other defects listed by nginx.org, including a use-after-free in HTTP/3 (CVE-2026-121810), another in the DNS resolver (CVE-2026-123634) and a third in the mail proxy module (CVE-2026-113425). For NGINX Plus, Wiz cites versions 37.0.8.1 or 37.3.0.1 against CVE-2026-123007, and 37.0.7.1 or 37.2.0.1 against CVE-2026-123633; F5’s bulletins are authoritative.

If the update cannot be immediate, CERT-FR and Wiz recommend disabling HTTP/2:

  • from NGINX 1.25.1 onwards, according to Wiz, add the http2 off; directive in the relevant server blocks and remove the http2 parameter from the listen directives;
  • validate the configuration with nginx -t, reload the service and make sure the old worker processes have actually stopped;
  • check with openssl s_client and the -alpn h2 option that the server no longer negotiates HTTP/2;
  • re-enable HTTP/2 once the fixed version is installed.

Wiz notes that a content delivery network or a web application firewall that terminates HTTP/2 itself can partly mitigate the risk, without eliminating it for direct access to the server.

Spotting a possible attack

Neither CERT-FR nor Wiz has published any confirmed indicator of compromise. Wiz suggests monitoring unexpected crashes of NGINX worker processes and any command launched by the service, which are general signals rather than evidence. For CVE-2026-123007, long-lived HTTP/2 connections transferring large volumes of data may warrant analysis. Armees.com also recommends taking an inventory of the versions and configurations in service, starting with internet-facing instances.

Frequently asked questions

Is my site vulnerable if it does not use HTTP/2?

According to CERT-FR and Wiz, both flaws require HTTP/2 to be enabled on the server. An NGINX server that only serves HTTP/1.1 is not exposed to these two defects, but it is still affected by the other fixes of 18 November: updating remains advisable.

Have shared hosting and cloud offerings already been patched?

It depends on each provider. For a hosted site, check the host’s announcements or contact its support. For a server managed in-house, including in a container, the update is the company’s responsibility.

How do I find out which version of NGINX is installed?

The nginx -v command displays the version in service. A version earlier than 1.30.7, or a 1.31 earlier than 1.31.9, must be updated. For NGINX Plus, the mapping is given in F5 bulletins K000163926 and K000163928.

Sources

Sur votre appareil

Comprendre cet article

L’analyse utilise l’intelligence locale du navigateur lorsqu’elle existe, sinon un résumé extractif. Le texte n’est envoyé à aucun service extérieur.

Facebook X LinkedIn

Ensuite A lire aussi

Free, no spam, one-click unsubscribe.