Technology

Two critical HTTP/2 vulnerabilities found in Nginx web server

Illustration: Tezkun / AI. Not a photograph of the event.

Five research teams, including Wiz Research and Rapid7, have independently discovered two critical vulnerabilities in the Nginx web server that allow remote code execution without authorization. F5, the developer of Nginx, released fixes on November 18.

The flaws have been assigned identifiers CVE-2026-123007 and CVE-2026-123633, both related to handling the HTTP/2 protocol. Wiz rated them at 9.2 on the CVSS 4.0 scale, while the European cybersecurity service CERT-EU rated them at 8.1. According to Wiz Research estimates, Nginx is used by more than 225 million websites, but only servers with HTTP/2 support enabled are susceptible to attack.

The first vulnerability, CVE-2026-123007, occurs when accounting for the data flow control window and leads to memory corruption. It has been present in the code since version 1.9.5, released in 2015. Wiz researchers demonstrated code execution even on a server that only serves static files, without a backend application or third-party modules. The second, CVE-2026-123633, is of the use-after-free type: a memory section is freed while it is still being used by a request. It affects configurations where Nginx operates as a reverse proxy.

Rapid7 has published a working method for exploiting CVE-2026-123007 for a Docker-based test environment, while Wiz does not yet plan to release its test exploits. According to CERT-EU, there are currently no confirmed cases of the vulnerabilities being used in real-world attacks.

In Nginx Open Source, both bugs have been eliminated in versions 1.30.7 (stable branch) and 1.31.9 (mainline). For Nginx Plus, versions 37.0.8.1 and 37.3.0.1 have been released, as well as 37.0.7.1 and 37.2.0.1 containing a fix for CVE-2026-123633.

What it means

Nginx Open Source releases starting from 1.9.5 through 1.31.8 inclusive are affected; CVE-2026-123633 affects versions starting from 1.19.7. The patched versions are 1.30.7 and 1.31.9. To exploit both bugs, HTTP/2 support must be enabled on the server.

Published 21 November 2026, 06:00 · No updates · Russian original

Discussion
  1. Loading comments…
No links or insults. One comment per 20 seconds.

Comments on this story live under its post in our Telegram channel. Comment on Telegram