The Library

NGINX Vulnerability CVE-2026-123007: Five Flaws Fixed in 1.31.9 and 1.30.7, Researchers Confirm Code Execution Through HTTP/2, and How to Check Your Server

NGINX has fixed five security flaws, and Wiz confirmed remote code execution through two critical HTTP/2 bugs on official builds. Here is what is confirmed, which versions are affected and how to check your servers this week.

Elite Performance Exclusive LLC 7 min read

Where Worldwide

NGINX Vulnerability CVE-2026-123007: Five Flaws Fixed in 1.31.9 and 1.30.7, Researchers Confirm Code Execution Through HTTP/2, and How to Check Your Server
On this page 8 sections

NGINX has fixed five security flaws in its web server software, and researchers at Wiz say two of them let them run their own code on official NGINX builds. If NGINX serves your website, app or API, or sits in front of one, check its version this week and update to 1.31.9 or later, or to 1.30.7 or later.

The Center for Internet Security (CIS) says there are no reports of attacks using these flaws yet. That gives businesses time to update before that changes. This article covers what is confirmed, what is still unknown and exactly what to check.

What happened with the NGINX vulnerability

According to the Wiz write-up, F5 published the NGINX security release on November 18, 2026, together with a coordinated public disclosure. The NGINX security advisories page now lists five CVE ids. All of them affect versions up to and including 1.31.8:

  • CVE-2026-123007
  • CVE-2026-123633
  • CVE-2026-123634, a use-after-free during response processing in the resolver
  • CVE-2026-121810, a use-after-free in HTTP/3
  • CVE-2026-113425, a use-after-free in the mail proxy module

A use-after-free is a memory bug: software keeps using a piece of memory after it has released it, and attackers can sometimes abuse that to crash a program or take control of it.

CIS issued its own advisory on 11/19/2026 under the title "Multiple Vulnerabilities in NGINX Could Allow for Remote Code Execution". Remote code execution means an attacker can make the server run commands of their choosing.

What is confirmed, what is claimed, and what is not known

Confirmed on NGINX's own advisory page: the five CVE ids, the vulnerable version ranges in the table below, and the fixed versions: 1.31.9 and later, and 1.30.7 and later. NGINX rates CVE-2026-123007 as major severity.

Reported by the researchers at Wiz: CVE-2026-123633 and CVE-2026-123007 are both rated Critical, with a CVSS 4.0 score of 9.2. Wiz writes: "Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server." Wiz also says it confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds. ASLR is a standard protection that shuffles where a program sits in memory, which makes attacks harder to aim. Getting past it is a key step toward a reliable attack.

Reported by CIS: "There are no reports of these vulnerabilities being exploited in the wild as of November 18, 2026."

Not known from these sources:

  • How the two HTTP/2 flaws work technically.
  • Whether an attacker needs any special access first.
  • Whether exploit code is public.
  • How serious NGINX rates the other three CVEs.
  • Whether servers that do not use HTTP/3, the mail proxy or the resolver are exposed to those three flaws.
  • Whether code execution works beyond the 1.31.7 and 1.31.8 builds Wiz tested.
  • Whether NGINX Plus and vendor-packaged NGINX builds are affected.

Which NGINX versions are affected

CVE What the sources say Vulnerable versions Fixed in
CVE-2026-123007 Needs HTTP/2 enabled, Critical, CVSS 4.0 9.2 (Wiz); major (NGINX) 1.9.5 to 1.31.8 1.31.9+, 1.30.7+
CVE-2026-123633 Needs HTTP/2 enabled, Critical, CVSS 4.0 9.2 (Wiz) 1.19.7 to 1.31.8 1.31.9+, 1.30.7+
CVE-2026-123634 Use-after-free in the resolver 0.6.18 to 1.31.8 1.31.9+, 1.30.7+
CVE-2026-121810 Use-after-free in HTTP/3 1.25.0 to 1.31.8 1.31.9+, 1.30.7+
CVE-2026-113425 Use-after-free in the mail proxy module 0.5.33 to 1.31.8 1.31.9+, 1.30.7+

These ranges go back a long way. If your server is not on 1.31.9 or later, or on 1.30.7 or later, assume it is in range for at least one of these flaws.

How to check if your NGINX server is vulnerable

  1. Check the version. Run nginx -v on each server. It prints the installed version.
  2. Compare it with the table. 1.31.9 or later, or 1.30.7 or later, is fixed. Anything older falls in the ranges above.
  3. See whether HTTP/2 is on. Run nginx -T 2>/dev/null | grep -i http2. A line such as http2 on; means HTTP/2 is enabled. Wiz says the two critical flaws need it.
  4. Note which other features you use. Check your config for a mail block, a resolver line, or HTTP/3 (quic or http3). The sources do not say whether leaving these features off removes the risk, so use this as a checklist, not a reason to wait.
  5. Ask about bundled copies. If NGINX came inside a hosting control panel, a container image or a vendor appliance, ask the supplier which NGINX version it includes and when they will ship 1.31.9 or 1.30.7.

What to do this week

Step What to do
1. Find every copy List every web server, reverse proxy, load balancer and container that runs NGINX, including ones nobody has touched in a while.
2. Patch the exposed ones first Update internet-facing servers with HTTP/2 enabled to 1.31.9 or later, or 1.30.7 or later.
3. Patch the rest The same versions fix all five flaws, so update internal servers too.
4. Restart and confirm Restart NGINX so the new version is actually running, then run nginx -v again. An update that is never restarted protects nothing; see Updated Is Not the Same as Patched.
5. Rebuild images Container images that pin an older NGINX keep shipping the old code until you rebuild and redeploy them.
6. Ask your suppliers Get a version number and a date from your host, panel or appliance vendor.

Do not treat turning off HTTP/2 as the fix. The sources we have describe no official workaround, and three of the five flaws are in other parts of NGINX. Updating is the fix.

Why this matters for a business website or network

If NGINX answers when a customer visits your website, every request goes through it. An attacker who can run code on that server could change what your site shows, read the traffic passing through it, or reach the rest of your network.

NGINX can also run inside other products and hosting setups without anyone on your team installing it by name, so finding every copy matters as much as updating. If you are not sure who is responsible for updating the servers your business depends on, read Who Is Patching the Software That Runs Your Business?. If you run your own servers, our self-hosting and infrastructure page explains how we set them up and look after them.

NGINX vulnerability questions people are asking

Which NGINX version fixes CVE-2026-123007?

1.31.9 or later, or 1.30.7 or later. The same versions fix all five flaws in this release.

Is the NGINX vulnerability being exploited?

Not as far as anyone has reported. CIS says there were no reports of exploitation in the wild as of November 18, 2026. That can change, so update now.

Do I need HTTP/2 enabled to be affected?

For CVE-2026-123007 and CVE-2026-123633, yes, according to Wiz. The other three flaws are in the resolver, HTTP/3 and the mail proxy module, and the sources do not say whether HTTP/2 matters for them.

Can I turn off HTTP/2 instead of updating?

The sources describe no official workaround. Turning off HTTP/2 would not address the three flaws in other parts of NGINX. Update to a fixed version.

How serious are these NGINX flaws?

Wiz rates the two HTTP/2 flaws Critical with a CVSS 4.0 score of 9.2, and says it confirmed remote code execution on official 1.31.7 and 1.31.8 builds. NGINX rates CVE-2026-123007 as major.

How do I check my NGINX version?

Run nginx -v on the server. Anything older than 1.31.9, unless it is 1.30.7 or later, needs updating.

Does this affect NGINX Plus?

The sources we checked do not say. If you run NGINX Plus, ask F5 directly.

The bigger lesson

The software that quietly sits in front of everything is the easiest to forget. The fix here is just a version update. The hard part is knowing every place NGINX runs, who is responsible for each copy, and confirming the new version is actually running.

To get your servers hardened and kept patched, see security hardening or request a quote.

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

Sources: NGINX security advisories; Wiz Research; CIS advisory.

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.