Resources / Alert

NGINX HTTP/2 Flaws CVE-2026-123007 and CVE-2026-123633: Who Is at Risk and What to Do

On 18 November 2026, NGINX fixed two memory flaws in its HTTP/2 code that can let an attacker run code on the server. Which versions are affected, which setups are at risk, what is not confirmed, and how to check your servers.

On this page · 6 sections
  1. Short answer
  2. Which setups are at risk
  3. What is confirmed and what is not
  4. How to tell from outside whether your NGINX speaks HTTP/2 and which version shows
  5. Three steps for a company without a security team
  6. Sources

In 30 seconds

What happens
On 18 November 2026, NGINX fixed two flaws in its HTTP/2 code that can let an outsider run code on the server; versions 1.30.7 and 1.31.9 fix them.
Who it affects
Companies whose websites, APIs or reverse proxies run NGINX with HTTP/2 switched on, including servers that only serve static files.
First step
Find every server running NGINX, check its version and whether HTTP/2 is on, and update to 1.30.7 or 1.31.9.
Our view
Our specialists have already prepared checks for these two NGINX flaws, and we are already finding affected systems at our clients and notifying them. NGINX often sits in front of company websites, installed years ago by someone who has since left. Updating is quick once you know where every NGINX server is, and that list is where most companies fall behind.

On 18 November 2026, the NGINX project released fixes for several flaws. Two of them, CVE-2026-123007 and CVE-2026-123633, are in the code that handles HTTP/2, a protocol every modern browser uses to load websites. Both can corrupt the server's memory, and researchers at Wiz, Xint and Rapid7, who found them independently, say this can lead to running code on the server.

Short answer

  • What happened: two memory flaws in NGINX's HTTP/2 code. F5, the company behind NGINX, rates both 9.2 out of 10 (CVSS 4.0), the score the US vulnerability database NVD shows.
  • Who is affected: NGINX Open Source 1.9.5 to 1.31.8 for CVE-2026-123007 and 1.19.7 to 1.31.8 for CVE-2026-123633, when HTTP/2 is switched on. Stable 1.30.7 and later are already fixed. NGINX Plus is affected too.
  • Is it being attacked: no attacks had been reported as of 19 November 2026, and neither flaw is in CISA's catalog of exploited vulnerabilities (KEV). Rapid7 has published working attack code for CVE-2026-123007.
  • What to do: update NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline, the branch with the newest features). If you cannot yet, switch HTTP/2 off until you can.

Checked on 19 November 2026 against the nginx.org security advisories and the researchers' published notes.

Which setups are at risk

The two flaws need different conditions, and that changes who should act first.

  • CVE-2026-123007 (memory corruption in HTTP/2 flow control): according to Wiz, it can be exploited on a server that only serves static files, with no application behind it and no extra modules. Rapid7's proof of concept ran code on NGINX 1.31.8 with HTTP/2 over TLS; Rapid7 says it took about 128 GB of HTTP/2 traffic: over a link slower than about 300 Mbit/s, NGINX's default one-hour limit on a connection cuts the attack off, and it is unlikely to work through a proxy in front of NGINX.
  • CVE-2026-123633 (use-after-free in HTTP/2): it needs NGINX working as a reverse proxy, passing requests on to another server. F5 also lists a low connection limit (worker_connections) as a condition; Xint, which tested it with proxy_pass, showed that an attacker can use up those slots by opening connections.

NGINX rates CVE-2026-123007 "major" and CVE-2026-123633 "medium" on its own scale, which is not CVSS. F5 also gives both 8.1 on the older CVSS 3.1 scale. The same release fixed other flaws too, in the DNS resolver, HTTP/3 and the mail proxy; updating covers them all.

What is confirmed and what is not

  • Confirmed by nginx.org: the affected and fixed versions above.
  • Partly confirmed: the NGINX Plus fixes. Wiz lists 37.0.8.1 and 37.3.0.1 for CVE-2026-123007, and 37.0.7.1 and 37.2.0.1 for CVE-2026-123633; for older Plus releases (R34 to R36), none of the sources we read names a fix. Check F5's advisories K000163926 and K000163928 for your release.
  • Not reported as of 19 November: attacks in the wild.

How to tell from outside whether your NGINX speaks HTTP/2 and which version shows

Two commands from any computer give a first answer (replace www.example.com with your site):

curl -sI https://www.example.com | grep -i "^server"
curl -sI --http2 https://www.example.com | head -1

The first command shows the Server header, for example "nginx/1.31.8". Many servers hide the number and show only "nginx", and the version shown may stay the same after a Linux distribution ships a patched package. The second shows "HTTP/2" if the server speaks it, or "HTTP/1.1" if not. In a browser, open the developer tools (F12), go to the Network tab and right-click the column headers to show the Protocol column: "h2" means HTTP/2.

If a CDN or load balancer sits in front, these answers describe that service, not your NGINX behind it. The server itself answers the final question: nginx -v shows the version, and searching the configuration for "http2" shows whether it is on. Servers set up for one project and then forgotten are the ones that miss updates; new vulnerabilities now arrive faster than yearly checks.

Three steps for a company without a security team

  1. Make the list. Ask whoever runs your sites, or your hosting provider, which servers run NGINX: websites, APIs, reverse proxies, test servers. Check each one from outside as shown above.
  2. Update. Install NGINX Open Source 1.30.7 or 1.31.9, or the patched package from your Linux distribution, and compare the installed package version with the fixed version named in the distribution's advisory; the NGINX version number alone can mislead. Restart NGINX so the new program is the one running.
  3. If you cannot update today, switch HTTP/2 off. On NGINX 1.25.1 and later, add http2 off; in the server blocks and also remove http2 from the listen lines; on older versions, remove it from the listen lines. Then reload and check that the old worker processes have exited. This covers only these two flaws, and services that need HTTP/2, such as gRPC, will stop working.

Forgotten servers miss kernel updates too; on 18 November we covered a Linux kernel flaw in TCP handling.


Sources

Get started

Know your risks before attackers find them.

Discover your external assets, identify security weaknesses and check for exposed corporate credentials with a free SeguriScan pilot. Get access to the platform, findings and reports to understand what needs attention.

  • Nothing to install
  • No access to your internal network
  • No active testing without your approval

We’ll contact you by email to discuss the pilot and agree on the next steps. No obligation to proceed. What’s included in the pilot →

By submitting this form, you acknowledge that IntruForce will process your personal data to respond to your request. See our Privacy Policy for details.