Security advisory · nginx

Memory corruption in nginx HTTP/2 can lead to remote code execution

nginx fixed five memory-corruption flaws on 18 November 2026. The main one, CVE-2026-123007, is in HTTP/2 flow control and can lead to remote code execution. nginx labels the flaws “major” and “medium”; F5, which issues the CVEs, scores the main one as high on CVSS 3.1 and critical on CVSS 4.0. The fix is to update to a patched release.

01 At a glance

What is affected

nginx, one of the most widely deployed web servers and proxies, disclosed and fixed five memory-corruption flaws in both NGINX Open Source and NGINX Plus on 18 November 2026. The one that carries the most risk is CVE-2026-123007: when nginx handles certain traffic, an HTTP/2 flow-control window can exceed its allowed threshold, which can corrupt memory and potentially lead to remote code execution. It affects configurations that use HTTP/2. The other four are use-after-free flaws in separate components. Updating is the remediation.

02 The five flaws

The five flaws and where they are

The severity labels in this table are nginx’s own (“major” or “medium”); nginx publishes no CVSS score.

The five flaws and where they are
CVEComponentnginx severity
CVE-2026-123007HTTP/2 flow control (memory corruption, potential RCE)major
CVE-2026-123633HTTP/2 (use-after-free)medium
CVE-2026-123634Resolver, processing responses (use-after-free)medium
CVE-2026-121810HTTP/3 (use-after-free)medium
CVE-2026-113425Mail proxy module (use-after-free)major
03 Severity by issuer

Severity for CVE-2026-123007, quoted with its issuer

nginx and F5 describe the main flaw on different scales. We quote each rating with the organization that assigned it.

Severity for CVE-2026-123007, quoted with its issuer
IssuerRating
nginx (project advisories)Labelled “major” (no CVSS score published)
F5 (CNA)CVSS 3.1 8.1 (high); CVSS 4.0 9.2 (critical)
04 Affected and fixed

Affected and fixed versions

Versions come from the nginx advisories and the CVE records. Update to the patched release on your branch; both patched releases are dated 18 November 2026.

Affected and fixed versions
BranchAffectedFixed in
Stable (1.30.x)earlier than 1.30.71.30.7
Mainline (1.31.x)1.31.0 through 1.31.81.31.9
05 Exploitation status

What is known about exploitation

As of 20 November 2026, none of these CVEs is in the CISA Known Exploited Vulnerabilities catalog, and neither nginx nor F5 publishes an active-exploitation status or a proof of concept in their primary advisories. We therefore make no claim of exploitation in the wild or of a public exploit. The reason to act promptly is different: nginx is deployed almost everywhere, F5 scores the main flaw as high to critical, and a fix is already available, so the sensible move is to patch before the picture changes.

06 Check yourself

How to check your exposure from outside

Run these checks only on servers you own or are authorized to test. They read the server’s banner and its TLS handshake; they send no payloads.

  1. Read the Server banner

    Look at the Server: nginx/x.y.z header in a response you already receive, and compare the version with the affected ranges: earlier than 1.30.7, or 1.31.0 through 1.31.8.

  2. Note whether HTTP/2 is offered

    In a normal TLS handshake, whether the server selects h2 through ALPN tells you if the HTTP/2 path that CVE-2026-123007 affects is in use. This is the handshake only.

  3. Treat a hidden version as tentative

    If the banner shows no version or only a partial one, such as nginx or nginx/1.24, you can see the server but cannot prove the build, so the finding is tentative.

  4. Remember forks

    Builds that re-number the version, including some forks and vendor distributions, fall outside a match by version number and need to be checked another way.

07 What to do

How to fix it

  • Update to the patched release on your branch: 1.30.7 on the stable branch, or 1.31.9 on the mainline branch. Both were published on 18 November 2026.
  • If you run a vendor package, apply the distribution’s update rather than comparing the upstream version number, which backports can make misleading.
  • Reducing exposure helps but is not a fix. Turning off HTTP/2 narrows the main flaw’s path, but the other issues sit in other components, so updating is the complete remedy.
08 Our view

How NorthBound looks at this

As part of tech stack intelligence, we recognize web-server software and match its version continuously to new CVEs, with issuer-specific severity context. For this advisory the external signal is the nginx version in the banner, with HTTP/2 negotiation as added context, so we keep a match tentative when the banner hides or trims the version. Our team reviews each match before it reaches you, and the check is a passive read of the banner and a handshake, never a payload against the server.

09 Primary sources

Sources

Find it before an attacker does.

Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.

Facts on this page verified 11 November 2026.