Takeaway: On November 18, 2026, the nginx project published nginx 1.31.9 (mainline) and nginx 1.30.7 (stable), security releases that fix 10 issues listed on the official nginx security advisories page. The two most widely discussed problems are in HTTP/2 handling: CVE-2026-123007, which nginx rates as major, and CVE-2026-123633, which nginx rates as medium. If you run nginx yourself, the practical step is to install one of those releases and start the new binary. A configuration reload of an old process is not the same thing.
The version numbers, severity labels, and vulnerable ranges below come from nginx.org. The official changelogs for 1.31.9 and 1.30.7 are both dated 18 Nov 2026. This is an nginx web-server update, not a WordPress core or plugin patch, and it is separate from this week’s NoisyTCP Linux kernel advisory and the Oxygen 6.2.2 builder update.
What nginx officially fixed
nginx.org lists 10 advisories as fixed in 1.31.9 and later. Nine of those are also fixed in 1.30.7 and later. The exception is CVE-2026-120993, a minor NULL pointer dereference tied to PROXY protocol version 2, which the advisory says affected only 1.31.4 through 1.31.8. That issue is not in the 1.30 stable changelog because the listed vulnerable range never included the 1.30 line.
nginx’s own severity ratings for the November 18 set are three major, four medium, and three minor:
- Major: CVE-2026-123007, memory corruption in HTTP/2 flow control (vulnerable 1.9.5–1.31.8). CVE-2026-118899, an infinite loop while reading a client request body over TLS 1.3 (vulnerable 1.13.0–1.31.8). CVE-2026-113425, a use-after-free in the mail proxy module (vulnerable 0.5.33–1.31.8).
- Medium: CVE-2026-123633, a use-after-free in HTTP/2 (vulnerable 1.19.7–1.31.8). CVE-2026-121810, a use-after-free in HTTP/3 (vulnerable 1.25.0–1.31.8). CVE-2026-123634, a use-after-free during response processing in the resolver (vulnerable 0.6.18–1.31.8). CVE-2026-120967, an SNI bypass when using client certificate validation in the stream module (vulnerable 1.25.5–1.31.8).
- Minor: CVE-2026-120993, noted above, fixed only in 1.31.9+. CVE-2026-125283, a buffer overflow when using alias with try_files (vulnerable 0.9.6–1.31.8). CVE-2026-123640, insufficient validation in the stream ssl_preread module (vulnerable 1.15.2–1.31.8).
The official changelogs stay within those limits. For CVE-2026-123007, nginx says a flow control window overflow in HTTP/2 might allow an attacker to cause a segmentation fault in a worker process, “or might have potential other impact.” For CVE-2026-123633, it says a use-after-free might occur in a worker process when using HTTP/2 if worker_connections were not enough. We are not going beyond that official wording here.
How third-party reports differ from nginx.org
Some research and press write-ups use stronger language than the nginx advisories. Wiz, which says it reported findings to F5 alongside other research teams, describes CVE-2026-123007 and CVE-2026-123633 as critical issues with a CVSS 4.0 score of 9.2 and says both require HTTP/2 to be enabled. A November 18 report in The Register repeats that critical rating and quotes a Wiz characterization of more severe outcomes than a worker crash.
Those are third-party assessments, not the labels on nginx.org, where CVE-2026-123007 is major and CVE-2026-123633 is medium. Operators should patch either way, but they should not treat a researcher CVSS score as if nginx itself published it.
The same Register report quotes an F5 spokesperson: “At this time, we have found no evidence of active exploitation of any of these vulnerabilities in the wild,” with a promise to share updates via myF5 if that changes. That is a point-in-time statement from November 18, 2026, not a guarantee.
What to install, including NGINX Plus
For nginx Open Source, the official download page now lists 1.31.9 as the mainline release and 1.30.7 as the stable release. If you are on the 1.31 mainline branch, move to 1.31.9 or later. If you are on the 1.30 stable branch, move to 1.30.7 or later. After the package or binary is in place, start the new nginx binary so workers actually run the fixed code.
F5 also issued updates for NGINX Plus. A November 18 advisory from the Canadian Centre for Cyber Security, AV26-1174, summarizes the F5 notice and lists NGINX Plus builds prior to 37.3.0.1, 37.0.8.1, 37.2.0.1, and 37.0.7.1, as well as Open Source builds prior to 1.31.9 and 1.30.7. Plus customers should apply the update that matches their own release branch and confirm the exact build in F5’s documentation, including the knowledge articles cited in that advisory (K000163926 and K000163928).
If you cannot upgrade immediately, some researchers have suggested temporarily disabling HTTP/2, because the two most-discussed issues are in HTTP/2 handling. That is a temporary workaround from third-party guidance, not a fix published on the nginx changelog, and it would not address the issues that are not tied to HTTP/2 — including the major TLS request-body loop, the mail proxy issue, the resolver issue, and the stream-module findings. The durable fix is still 1.31.9, 1.30.7, or the matching Plus build.
What this means for WordPress and hosted sites
Many WordPress sites sit behind nginx, either on a self-managed VPS or through a host that uses nginx as the front-end web server or reverse proxy. This update does not land through the WordPress dashboard. If you administer the web server, install the new nginx package and start the new binary. If a host or platform manages nginx for you, ask whether it has already moved to 1.31.9, 1.30.7, or the corresponding NGINX Plus build.
Key facts
| Item | What official sources say |
|---|---|
| Date | 18 November 2026, according to the nginx 1.31.9 and 1.30.7 changelogs and the current download page. |
| Fixed Open Source versions | nginx 1.31.9 (mainline) and nginx 1.30.7 (stable). |
| How many issues | 10 advisories fixed in 1.31.9+. Nine of those are also fixed in 1.30.7+. CVE-2026-120993 is mainline-only (1.31.4–1.31.8). |
| nginx severity | Three major (CVE-2026-123007, CVE-2026-118899, CVE-2026-113425), four medium, three minor. |
| HTTP/2 issues | CVE-2026-123007 (major) and CVE-2026-123633 (medium). Official changelogs describe a possible worker segmentation fault or use-after-free, with “potential other impact” noted for CVE-2026-123007. |
| NGINX Plus | The Canadian Centre for Cyber Security’s November 18 summary of F5’s notice lists Plus builds prior to 37.3.0.1, 37.0.8.1, 37.2.0.1, and 37.0.7.1 as affected. Confirm the correct branch in F5’s articles. |
| Exploitation | An F5 spokesperson told The Register on November 18 that F5 had found no evidence of active exploitation in the wild at that time. |
| What to do | Install the fixed release for your branch and start the new binary. A reload of the old process is not sufficient. |
FAQ
Which nginx versions should I install?
Install nginx 1.31.9 or later if you are on the mainline branch, or nginx 1.30.7 or later if you are on the 1.30 stable branch. NGINX Plus customers should install the F5 build that matches their release line and confirm it in official F5 documentation.
Are these officially rated critical?
Not on nginx.org. The project’s highest official rating in this set is major, used for CVE-2026-123007, CVE-2026-118899, and CVE-2026-113425. Some research firms and news reports have called the two HTTP/2 issues critical and assigned a 9.2 CVSS 4.0 score. That is their assessment, not nginx’s advisory label.
Do I need to upgrade if I already run a recent 1.31 or 1.30 build?
Yes, if you are still below 1.31.9 or 1.30.7. Several of the listed ranges go up through 1.31.8, including the major HTTP/2 and TLS request-body issues.
Is a reload enough after I upgrade the package?
No. A configuration reload keeps the already-running binary in memory. After you install 1.31.9, 1.30.7, or a fixed Plus build, start the new nginx binary so the patched code is what answers requests.
Does turning off HTTP/2 fully protect a server?
No. Researchers have suggested temporarily disabling HTTP/2 if you cannot patch right away, because CVE-2026-123007 and CVE-2026-123633 are HTTP/2 issues. That workaround would not cover the other November 18 findings, including problems in TLS request-body handling, the mail proxy, the resolver, HTTP/3, and the stream module.
Does this patch WordPress itself?
No. It updates the nginx web server or reverse proxy that may sit in front of WordPress. Site owners who do not manage nginx should check with their host. The WordPress admin update screen will not apply this fix.
Is CVE-2026-120993 fixed in nginx 1.30.7?
The official advisory lists that issue as vulnerable only in 1.31.4–1.31.8 and not vulnerable in 1.31.9 and later. It is not listed in the 1.30.7 changelog. If you are on the 1.30 stable line, the other nine advisories are the ones 1.30.7 addresses.
Has this been exploited in the wild?
An F5 spokesperson told The Register on November 18, 2026, that F5 had found no evidence of active exploitation at that time and would share updates via myF5 if more became known. Check F5 and nginx.org for later statements rather than treating that comment as final.

Leave a Reply
You must be logged in to post a comment.