The Library

NGINX HTTP/2 Vulnerability: CVE-2026-123633 and CVE-2026-123007 Can Lead to Remote Code Execution, Fixed in 1.31.9 and 1.30.7, and How to Turn HTTP/2 Off

Two memory-safety flaws in how NGINX handles HTTP/2 traffic can be turned into remote code execution, researchers confirmed. Here are the affected versions, the fixed releases and the stop-gap if you cannot update yet.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

NGINX HTTP/2 Vulnerability: CVE-2026-123633 and CVE-2026-123007 Can Lead to Remote Code Execution, Fixed in 1.31.9 and 1.30.7, and How to Turn HTTP/2 Off
On this page 7 sections

Two newly disclosed flaws in how NGINX handles HTTP/2 traffic can be turned into remote code execution, according to Wiz Research, one of five teams that found them independently. If your website, web app or API runs on NGINX, update to version 1.31.9 or 1.30.7 this week, or turn HTTP/2 off until you can.

What happened with the NGINX HTTP/2 vulnerability

On November 18, 2026, F5 published a security release for NGINX and the flaws were disclosed publicly in a coordinated way, according to the timeline in the Wiz Research write-up. The two flaws are tracked as CVE-2026-123633 and CVE-2026-123007, and both appear on the official nginx.org security advisories page.

Wiz describes the root cause in one line: "Both vulnerabilities are memory-safety issues in how NGINX handles HTTP/2 traffic."

  • CVE-2026-123633 is a use-after-free. In plain terms, NGINX frees the memory for a connection while a request still needs it.
  • CVE-2026-123007 is a flow-control accounting error. NGINX miscounts how much data it should handle, which leads to an invalid memory copy.

Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint each found the flaws independently.

Which NGINX versions are affected

This table comes from the nginx.org security advisories page.

CVE What it is Vulnerable versions Fixed versions nginx.org rating
CVE-2026-123633 Use-after-free in HTTP/2 connection handling 1.19.7 through 1.31.8 1.31.9 and later, 1.30.7 and later Medium
CVE-2026-123007 Flow-control error causing an invalid memory copy 1.9.5 through 1.31.8 1.31.9 and later, 1.30.7 and later Major

In practice: any version from 1.19.7 through 1.31.8 is inside the CVE-2026-123633 range, and any version from 1.9.5 through 1.31.8 is inside the CVE-2026-123007 range. The advisory lists no fix for versions inside these ranges other than moving to 1.30.7 or 1.31.9 or later.

What is confirmed and what is not

Confirmed by the primary sources:

  • Both CVEs, the vulnerable version ranges and the fixed versions, as listed on nginx.org.
  • Code execution has been demonstrated. Wiz writes: "We confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds." An ASLR bypass means the researchers got past a standard memory protection that normally makes this kind of attack harder.
  • Wiz rates both flaws Critical, with a CVSS 4.0 score of 9.2.

Where the sources differ: nginx.org rates CVE-2026-123633 as medium and CVE-2026-123007 as major. Wiz rates both as Critical. The sources we checked do not explain the gap. Our advice is the same either way: a flaw with demonstrated code execution belongs at the top of this week's list.

Not known from the sources we verified:

  • Whether attackers are exploiting these flaws in the wild. Neither source says so, and neither says they are not.
  • Whether an attacker needs any login or special access. The sources we checked do not state this. Until your servers are updated, plan as if anyone who can reach the server could try.
  • Whether code execution works on versions older than 1.31.7. Wiz demonstrated it on 1.31.7 and 1.31.8 only, but nginx.org still lists the older versions as vulnerable.
  • Whether a server with HTTP/2 already turned off is exposed. The flaws are in HTTP/2 handling and the published stop-gap is turning HTTP/2 off, but we could not confirm a plain statement either way.

What to do this week: NGINX patch checklist

  1. List every place NGINX runs. Website servers, app and API backends, load balancers, containers and any server your developer or hosting company set up for you.
  2. Check the version. On each server, run nginx -v and note the number.
  3. Compare against the table. Anything from 1.9.5 through 1.31.8 is in range for at least one of the flaws.
  4. Update to a fixed release. Install 1.31.9 or later, or 1.30.7 or later. Then run nginx -v again and make sure the running service was restarted on the new version. A package that is installed but not running yet does not protect you, which is the point of our post Updated Is Not the Same as Patched.
  5. If you cannot update today, turn HTTP/2 off. Wiz's interim advice: "Set http2 off; in affected server blocks on NGINX 1.25.1 or later, and remove the http2 parameter from any listen directives." Search your NGINX configuration files for http2 to find every spot, test the configuration with nginx -t, then reload.
  6. Treat the workaround as temporary. Turning HTTP/2 off is a stop-gap. The fix is the updated version.
  7. Ask your providers in writing. If a hosting company, agency or vendor runs NGINX for you, ask which version is running and the date it was updated.

Why the NGINX RCE vulnerability matters for a business website

NGINX is the software that receives web traffic before your site or app ever sees it. A flaw that leads to code execution there is not a cosmetic problem: whoever runs code on that server may be able to reach what the server can reach, such as site files, database connections, API keys and customer records.

This is also the kind of software nobody thinks about. A website gets built, the server gets set up, and the web server underneath keeps running the version it shipped with. If nobody on your side owns that layer, a fix released on November 18 can sit uninstalled for months. We wrote about that gap in Who Is Patching the Software That Runs Your Business?, and it applies here directly.

If you host your own servers, this is a good moment to confirm you have a routine for checking advisories and applying updates, not just a server that works. Our self-hosting and infrastructure page covers what that looks like.

NGINX vulnerability questions people are asking

Is my NGINX server vulnerable to CVE-2026-123633?

If nginx -v shows a version from 1.19.7 through 1.31.8, nginx.org lists it as vulnerable. Versions 1.31.9 and later and 1.30.7 and later are not vulnerable.

What version of NGINX fixes CVE-2026-123007?

NGINX 1.31.9 or later, or 1.30.7 or later. The vulnerable range for this flaw is wider, going back to 1.9.5.

Is the NGINX HTTP/2 exploit being used by attackers?

The sources we verified do not say. What is confirmed is that Wiz Research achieved remote code execution on official 1.31.7 and 1.31.8 builds.

How do I disable HTTP/2 in NGINX?

On NGINX 1.25.1 or later, add http2 off; to the affected server blocks, and remove the http2 parameter from any listen lines. Test the configuration and reload.

Why does nginx.org call it medium when Wiz says critical?

nginx.org rates CVE-2026-123633 as medium and CVE-2026-123007 as major, while Wiz gives both a CVSS 4.0 score of 9.2. The sources do not explain the difference. Update either way.

Who found the NGINX HTTP/2 flaws?

Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint, each independently. F5 released the fixes on November 18, 2026.

Do I need to do anything if a host runs my site?

Yes. Ask them which NGINX version is running and when it was updated. You are still responsible for the site, even if someone else runs the server.

The bigger lesson

The software that answers your web traffic is part of your business, even if you never see it. Five research teams finding the same flaws independently is a reminder that bugs in widely deployed software get found, and the only thing that protects you is a server that is actually running the fixed version. Know where NGINX runs, know who updates it, and check the version this week.

Want someone to check your servers and keep them patched? See security hardening or request a quote.

Get security alerts like this by email, along with our free checklist, at security alerts.

Sources: Wiz Research: NGINX HTTP/2 RCE vulnerabilities; nginx.org security advisories.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.