NGINX CVE-2026-123007 patch — 1.30.7, 1.31.9; restart it
The NGINX HTTP/2 remote code execution flaws CVE-2026-123007 and CVE-2026-123633 are fixed in nginx 1.30.7 (stable) and 1.31.9 (mainline), released on November 18, 2026. NGINX Plus is fixed in 37.0.8.1 and 37.3.0.1. After upgrading, a reload is not enough: the master process keeps the old binary, so the service needs a full restart. F5 rates both flaws 9.2 under CVSS 4.0, and CVE-2026-123007 affects every version from 1.9.5, where HTTP/2 first appeared in 2015, through 1.31.8. Ubuntu, Debian and RHEL backport the fix without changing the version number, so check the package version, not the output of nginx -v. If you cannot upgrade yet, turning HTTP/2 off blocks these two flaws. As of November 19, 2026 there were no reports of attacks in the wild and neither CVE was in the CISA Known Exploited Vulnerabilities catalog.
The three lines
- Versions — nginx 1.30.7 (stable) and 1.31.9 (mainline); NGINX Plus 37.0.8.1 and 37.3.0.1, all dated November 18, 2026. Distro packages may keep the old version number, so compare the full package version with the vendor advisory
- Action — upgrade, then restart, not reload. If you cannot upgrade, set http2 off. That blocks only CVE-2026-123007 and CVE-2026-123633, and it breaks gRPC clients
- Status — as of November 19, 2026: no reported attacks, not on CISA KEV. The public Rapid7 proof of concept needs x86-64 glibc, roughly 128 GB of traffic and an ASLR bypass, and lands as the worker process
Key questions
- NGINX CVE-2026-123007 patch version
- **nginx 1.30.7 (stable) and 1.31.9 (mainline), released November 18, 2026. Restart the service fully after upgrading.** | Product | Fixed version | Note | |---|---|---| | NGINX Open Source, stable | 1.30.7 | Official Docker image nginx:1.30.7 | | NGINX Open Source, mainline | 1.31.9 | Official Docker image nginx:1.31.9 | | NGINX Plus | 37.0.8.1, 37.3.0.1 | CVE-2026-123633 alone is also fixed in 37.0.7.1 and 37.2.0.1 | | NGINX Ingress Controller (F5) | 5.8.0 | Confirmed only through one source summary | | Distro packages | Varies | Backported without a version bump; check the package version |
- nginx HTTP/2 vulnerability workaround http2 off
- **Turning HTTP/2 off blocks CVE-2026-123007 and CVE-2026-123633. The other flaws need their own steps, and gRPC stops working.** | nginx version | How to turn HTTP/2 off | |---|---| | 1.25.1 and newer | Add `http2 off;` to each server block or once in the http block, and remove http2 from listen lines | | 1.9.5 to 1.25.0 | Remove the http2 flag from listen lines | | Verify | `curl -so /dev/null -w %{http_version} --http2 https://example.com/` prints 1.1 when it is off | | Side effect | gRPC clients break |
- Is CVE-2026-123007 being exploited
- **As of November 19, 2026 there were no reports of attacks and it was not in CISA KEV. One public proof of concept exists.** | Item | Status as of November 19, 2026 | |---|---| | Attacks in the wild | None reported (Tenable, ThreatDefence) | | CISA KEV | Not listed | | Public proof of concept | Published by Rapid7 on November 18 for CVE-2026-123007 | | Its constraints | x86-64 glibc, about 128 GB of HTTP/2 traffic, an ASLR bypass | | Privilege gained | The nginx worker process, not root | | Wiz and Xint | Hold working exploits and are not publishing them |
The two HTTP/2 remote code execution flaws in NGINX, CVE-2026-123007 and CVE-2026-123633, are fixed in nginx 1.30.7 (stable) and 1.31.9 (mainline). F5 published both on November 18, 2026 as an out-of-band release, outside its normal schedule. The commercial NGINX Plus is fixed in 37.0.8.1 and 37.3.0.1. F5 rates both flaws 9.2 under CVSS 4.0, and neither needs a login: network access to the server is enough.
Two things are easy to get wrong here. First, a reload after the upgrade does not apply the fix. Reload re-reads the configuration and starts new workers, but the master process goes on holding the old binary. Second, nginx -v is the wrong check on Ubuntu, Debian or RHEL. Distributions backport the fix into the version they already ship, so a patched server still reports 1.24.0 or 1.18.0. This page covers which version to move to, how to tell whether a server is affected, and what to do if the upgrade has to wait, from a defender's point of view.
1. Which versions are fixed — 1.30.7 and 1.31.9; Plus 37.0.8.1 and 37.3.0.1
The table reconciles four write-ups: Tenable's FAQ, the per-distro patch tracker at ma.ttias.be, the post by Xint, the security firm that found the bugs, and ThreatDefence's patching guide.
| Product | Affected | Fixed | Note |
|---|---|---|---|
| NGINX Open Source, stable | 1.9.5 up to, not including, 1.30.7 | 1.30.7 | Released November 18, 2026 |
| NGINX Open Source, mainline | Through 1.31.8 | 1.31.9 | Same day |
| Official Docker images | As above | nginx:1.30.7, nginx:1.31.9 | Pull the new image and recreate the container |
| NGINX Plus | 37.x and older branches (see below) | 37.0.8.1, 37.3.0.1 | CVE-2026-123633 alone is also fixed in 37.0.7.1 and 37.2.0.1 |
| NGINX Ingress Controller (F5) | — | 5.8.0 | Seen only in a summary of ThreatDefence |
| Community ingress-nginx | — | No fixed release | Said to have been archived in March 2026; single source |
| Distro packages | Varies | See section 2 | Backports that do not change the version number |
Three points in that table deserve a second look.
NGINX Plus has different fixed builds per CVE. To close CVE-2026-123007 as well, you need 37.0.8.1 or 37.3.0.1. Builds 37.0.7.1 and 37.2.0.1 fix only CVE-2026-123633. A server sitting on 37.0.7.1 is still exposed to the flaw with the wider range.
Sources disagree on which Plus branches are affected. Tenable says R34 through R36 and 37.x are affected and that R34 to R36 get no fix, so those customers must move to 37.x. ma.ttias.be and ThreatDefence say R33 and 37.x. We could not open F5 advisory K000164058 to settle it. Anyone on a Plus branch older than 37.x should look up their branch in the advisory directly.
The release fixes ten CVEs, not two. Five were reported by Xint (the two HTTP/2 bugs, plus the resolver, HTTP/3 and the mail proxy), and five more ride along. Section 5 lists them. That is why a server that does not use HTTP/2 still needs the upgrade.
2. Distro packages — check the package version, not nginx -v
Most servers run the nginx package from their distribution, not a build from nginx.org. Distributions rarely bump the upstream version for a security fix. They copy the fix into the version they already ship. So nginx -v can print 1.24.0 on a patched machine, and the same number on an unpatched one. The full package version string is what counts.
The table below is what ma.ttias.be last checked on November 20, 2026 at 19:04 UTC. The author says it will not be updated again. Anything marked as unfixed may have changed since, so read the vendor advisory before acting on it.
| Distribution | Status | Fixed package version |
|---|---|---|
| Ubuntu 26.10 / 26.04 | Fixed (USN-9159-1) | 1.30.4-7ubuntu1.2 / 1.28.3-2ubuntu1.13 |
| Ubuntu 24.04 / 22.04 | Fixed (USN-9159-1) | 1.24.0-2ubuntu7.20 / 1.18.0-6ubuntu14.23 |
| Ubuntu 20.04 / 18.04 / 16.04 (ESM, Pro) | Fixed | 1.18.0-0ubuntu1.7+esm5 / 1.14.0-0ubuntu1.11+esm6 / 1.10.3-0ubuntu0.16.04.5+esm11 |
| Debian 13 / 12 | Fixed (DSA-6642-1 / DLA-4918-1) | 1.26.3-3+deb13u11 / 1.22.1-9+deb12u11 |
| Debian sid | Fixed | 1.30.6-4 |
| Debian forky | No fix | 1.30.6-3 is vulnerable |
| RHEL 10 | Fixed (RHSA-2026:100744) | 1.26.3-16.el10_3.3 |
| RHEL 9 | Fixed (RHSA-2026:100748) | Default 1.20.1-32.el9_9.2; module streams 1.24.0-9.module+el9.9.0 and 1.26.3-10.module+el9.9.0 |
| RHEL 8 | Fixed (RHSA-2026:100747) | nginx:1.24 stream 1.24.0-3.module+el8.10.0 |
| AlmaLinux 10 / 9 | Fixed | 1.26.3-16.el10_3.1.alma.2 / 1.20.1-32.el9_9.1.alma.3 |
| AlmaLinux 8 | No advisory yet | No fix |
| Oracle Linux 10 | Fixed | 1.26.3-16.0.1.el10_3.3 |
| Oracle Linux 9 and 8 module streams | Fixed | 1.24.0-9.0.2.module+el9.9.0, 1.26.3-10.0.2.module+el9.9.0, 1.24.0-3.0.2.module+el8.10.0 |
| Oracle Linux 9 default package | No fix yet | No advisory issued |
| Amazon Linux 2023 | Fixed (ALAS2023-2026-3494) | 1.30.7-1.amzn2023.0.1 |
| Amazon Linux 2 (nginx1 extra) | Fixed | 1.30.7-1.amzn2.0.1 |
| Alpine 3.24 and edge | Fixed | 1.30.7-r0 |
| Alpine 3.23 and 3.22 / 3.21 | Fixed (backport) | 1.28.3-r8 / 1.26.3-r4 |
| Arch Linux | Fixed | nginx 1.30.7-1, nginx-mainline 1.31.9-1 |
| Fedora 43 / 44 / 45 | No fix | 1.30.6 is vulnerable |
| openSUSE Tumbleweed | Fixed | 1.31.9-1.1 |
| SLES 15 SP7 / 16 | In progress | 15 SP7 fix (1.21.5-150600.10.30.1) in QA |
| openSUSE Leap 16.0 / 16.1 | No fix | Affected |
ThreatDefence, writing on November 19, listed Ubuntu, Debian, Red Hat and SUSE as pending. A day later most of them had shipped, so this article follows the later table. That much movement in one day is the reason to re-check whatever you read here against the vendor.
Teams running Alpine-based containers have one more step. A fixed package in the base image does nothing for images already built or containers already running. Rebuild the image and replace the containers.
3. Is my server affected — version, HTTP/2, and the binary that is actually running
There are four things to establish: the installed version, whether HTTP/2 is on, whether HTTP/2 is reachable from outside, and whether the running process is the new binary.
| Step | What to check | What it tells you |
|---|---|---|
| 1 | nginx version | 1.9.5 through 1.31.8 is in range, though a distro build may already be backported |
| 2 | Package version | At or above the fixed version in section 2 or the vendor advisory |
| 3 | HTTP/2 module and config | If the module is compiled in and http2 appears in the config, the two HTTP/2 flaws apply |
| 4 | HTTP/2 from outside | An ALPN result of h2 means it is reachable. Behind a CDN, test the origin IP directly |
| 5 | Running binary | A (deleted) suffix on the process exe link means the old binary is still running |
The commands, taken from Xint and ma.ttias.be:
- Version:
nginx -v - Package version:
dpkg -l nginxon Debian and Ubuntu,rpm -q nginxon the RHEL family,apk info -v nginxon Alpine - HTTP/2 module compiled in:
nginx -V 2>&1 | grep -- --with-http_v2_module - HTTP/2 enabled in the config:
nginx -T 2>/dev/null | grep -n http2 - HTTP/2 reachable from outside: run
openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/nulland look forALPN protocol: h2in the output - Running binary:
sudo ls -l /proc/$(pgrep -o -x nginx)/exe
The last command is the reason for this article's headline. Upgrading the package replaces the nginx file on disk. But nginx -s reload or systemctl reload nginx leaves the master process in place, re-reads the configuration and starts fresh workers. What the master holds in memory is still the old binary, and its exe link now points at a file that no longer exists, which is why (deleted) appears at the end. Tenable, ma.ttias.be and Xint all say the same thing: a reload is not enough; a full restart is required. Run systemctl restart nginx, then repeat the command and confirm that (deleted) is gone.
On servers behind a CDN or another proxy, two sources put it slightly differently. Tenable says the public proof of concept is unlikely to work behind a proxy that terminates HTTP/2. ma.ttias.be says the origin IP must still not answer on port 443 directly. These fit together. The front end reduces the risk while traffic goes through it, but an attacker who finds the origin IP does not go through it. That is why step 4 should be run against the origin address.
4. If you cannot upgrade yet — http2 off, and what it does not cover
Upgrading and restarting is the only fix. If a maintenance window is days away, turning HTTP/2 off buys time.
| Step | How | What it blocks | Limits |
|---|---|---|---|
| Turn HTTP/2 off (1.25.1 and newer) | Add http2 off; in each server block or once in the http block, and remove http2 from listen lines | CVE-2026-123007, CVE-2026-123633 | gRPC clients break. The other eight CVEs remain |
| Turn HTTP/2 off (1.9.5 to 1.25.0) | Remove the http2 flag from listen lines | Same | Same |
| Resolver flaw | Point proxy_pass at a fixed upstream group and set mirror off where mirroring is not needed | CVE-2026-123634 | Tenable and Xint both say turning mirror off alone is not enough |
| Turn HTTP/3 off | Remove quic listeners, set http3 off; and add add_header Alt-Svc 'clear' always; | CVE-2026-121810 | Clients fall back to HTTP/2 or 1.1 |
| Restrict the mail proxy | Bind mail listeners to loopback or limit access with a firewall | CVE-2026-113425 | Hosts inside the allowed range still reach it |
| Hide the origin | Allow port 443 on the origin only from the CDN's ranges | Direct outside access | The flaw itself remains |
| Monitor | Log long-lived connections with unusually high inbound bytes, and shells spawned by worker processes | Detection | Not prevention |
To confirm HTTP/2 is off, run curl -so /dev/null -w '%{http_version}\n' --http2 https://example.com/. It prints 1.1 when HTTP/2 is disabled. Because this is a configuration change, a reload does apply it. Keep the distinction straight: a reload is enough for a config change, and a restart is needed for a new binary.
Turning HTTP/2 off has a cost. gRPC runs only over HTTP/2, so any service that nginx fronts for gRPC stops working. Ordinary web traffic falls back to HTTP/1.1 and keeps working, without the benefit of carrying many requests on one connection.
Everything in this table is temporary. Xint notes that mirror_request_body on stops its own test exploit for the resolver flaw without fixing the bug. A mitigation closes one known path, nothing more.
5. What was fixed — two HTTP/2 flaws and eight others
The November 18 release covers ten CVEs. The first five were reported by Xint. According to Tenable and ThreatDefence, F5 scores all five at 9.2 under CVSS 4.0 and 8.1 under CVSS 3.1.
| CVE | Where and what | Conditions | First affected version |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control. A window value wraps around, causing heap reads and writes out of bounds | HTTP/2 enabled. Applies even to a server that only serves static files | 1.9.5 |
| CVE-2026-123633 | HTTP/2 use-after-free | HTTP/2 plus proxying to a backend, with connection slots nearly exhausted | 1.19.7 (Xint, ThreatDefence) or 1.9.5 (ma.ttias.be) |
| CVE-2026-123634 | Resolver use-after-free | proxy_pass with request-time DNS, plus mirror or SSI | 1.13.4 (Xint) or 0.6.18 (ThreatDefence summary) |
| CVE-2026-121810 | HTTP/3 (QUIC) use-after-free | HTTP/3 plus an upstream proxy | 1.25.0 |
| CVE-2026-113425 | Mail proxy use-after-free | proxy on with auth_http. No credentials needed | 0.5.15 (Xint) or 0.5.33 (ThreatDefence summary) |
All five run through 1.31.8. Use-after-free means touching memory after it has been handed back; we explained the bug class on November 14, 2026 in "What is use-after-free (UAF) — a memory mistake behind about a third of Chrome's high-severity bugs."
The starting version for CVE-2026-123633 is disputed. Xint and ThreatDefence say 1.19.7. ma.ttias.be says every nginx from 1.9.5 to 1.31.8 with HTTP/2 on. For a defender the answer is the same either way, because the same server is already in range for CVE-2026-123007 from 1.9.5. Treat the whole 1.9.5 to 1.31.8 span as affected.
The bug class of CVE-2026-123007 is also worded two ways: integer overflow at Xint, integer underflow at ThreatDefence. Both describe an unsigned value wrapping past its limit, named from opposite directions.
Tenable names the five other CVEs in the same release.
| CVE | Component | CVSS 4.0 |
|---|---|---|
| CVE-2026-118899 | TLSv1.3 handling | 8.7 |
| CVE-2026-120993 | ngx_stream_ssl_module | 6.9 |
| CVE-2026-125283 | map directive and regex matching | 6.9 |
| CVE-2026-123640 | ngx_stream_ssl_preread_module | 6.9 |
| CVE-2026-120967 | ngx_stream_ssl_module | 6.3 |
None of the sources gave affected version ranges for these five. For how to read the scores, see our October 6, 2026 piece, "What CVSS is — why GitLab's critical flaw scored 9.9, not 10."
The "ten-year-old flaw" label comes from the range of CVE-2026-123007. The code has been there since HTTP/2 support landed in nginx 1.9.5 in 2015, a little over eleven years before November 2026. Xint says the development master branch was still vulnerable on November 10, 2026.
Xint also reported a use-after-free in the Linux kernel's SCTP code. As of November 19, 2026 it had no CVE and no patch, and Xint says it is holding back most details until a kernel fix exists. Hosts that do not use SCTP can keep the module from loading with a line reading install sctp /bin/false under /etc/modprobe.d/. That does not unload a module that is already loaded, and it does nothing where SCTP is built into the kernel.
6. Exploitation and exposure — no reported attacks, and a public proof of concept with many conditions
Here is what is established and what is not, as of November 19, 2026.
| Who | What they did or said | When |
|---|---|---|
| F5 | Out-of-band release 1.30.7 and 1.31.9, advisory K000164058 | November 18, 2026 |
| Tenable, ThreatDefence | No reports of attacks; not in CISA KEV | As of November 19 |
| Rapid7 | Published a proof of concept for CVE-2026-123007 on GitHub, shown against nginx 1.31.8 in Docker with HTTP/2 over TLS | November 18 |
| Censys | Reproduced code execution for CVE-2026-123007 with the Rapid7 code, as the worker and not root. Three of the use-after-free bugs did not yield code execution in its lab, and CVE-2026-121810 was not reproduced | Tenable update of November 19 |
| Wiz | Built working exploits for CVE-2026-123007 and CVE-2026-123633 and is not releasing them | November 18 |
| Xint | Published demo videos with the final steps left out | November 18 |
Tenable relays Rapid7's own description of its proof of concept as constrained. It needs an x86-64 glibc target, about 128 GB of HTTP/2 traffic and a bypass of address space layout randomization. When it works, it lands as the nginx worker process, not as root. Tenable adds that it is unlikely to work behind a proxy that terminates HTTP/2, or over a connection too slow to deliver the data within nginx's one-hour connection limit.
None of that is a reason to wait. The constraints belong to that published code, not to the flaw. Wiz and Xint hold separate exploits they have not released. And where Xint says each of its five bugs leads to remote code execution on its own, Censys could not get code execution from three of the use-after-free bugs. That is a disagreement about reproducibility, not a finding of safety. The fix and the description of the bug went public on the same day, so attackers started from the same information as defenders. Our November 18, 2026 explainer, "What is patch diffing — why a fix is a map, 63 days to −7," describes how a published fix becomes a guide for attackers.
Two exposure figures are in circulation. They measure different things and should not be set side by side.
| Source | Date | What was counted | Figure |
|---|---|---|---|
| Censys, via Tenable | November 18, 2026 | NGINX services on an affected version with HTTP/2 enabled | About 9 million |
| Shodan, via Xint | November 10, 2026 | All hosts identified as nginx | 56.7 million |
| Shodan, via Xint | Same day | Of those, hosts that reported a version | 11.94 million (21.1%) |
| Shodan, via Xint | Same day | Of hosts reporting a version, share in 1.9.5 to 1.31.8 | 98.9% |
Both may overstate the problem. A version string cannot show whether a distribution has backported the fix. Xint says as much, and Tenable notes that the Censys figure may include distro builds that are already patched.
The disclosure timeline, for the record:
| Date | Event | Source |
|---|---|---|
| 2015 | HTTP/2 arrives in nginx 1.9.5, the start of the CVE-2026-123007 range | Tenable, Xint and others |
| October 11, 2026 | Xint finds the bugs | Tenable, Xint |
| October 16 | Xint reports through HackerOne | Tenable, Xint |
| October 27 | Reports reach F5's nginx team | Xint |
| November 9–10 | nginx asks Xint to validate the patch; Xint completes validation | Xint |
| November 18 | 1.30.7 and 1.31.9 released; F5 advisory; Rapid7 analysis and proof of concept; Xint and Wiz write-ups | All four sources |
| November 19 | No reported attacks; not on KEV | Tenable, ThreatDefence |
| November 20 | ma.ttias.be distro table last checked, 19:04 UTC | ma.ttias.be |
Xint says one of its researchers found CVE-2026-123007 while preparing for a competition, and that a fully automated Xint scan found the other four without human guidance. Credit is not tidy. Tenable says Wiz, Rapid7, Xint and others reported CVE-2026-123007 independently. Xint lists CVE-2026-123633 among its five, while the ThreatDefence summary says Wiz reported it on October 21 and that F5 replied another team had got there first. The name "NGINX2Root" is Xint's; F5 and nginx.org do not use it.
7. Frequently asked questions
My server reports nginx 1.24.0. Is it vulnerable? The number alone cannot tell you. The fixed package on Ubuntu 24.04 is still 1.24.0, with the full version 1.24.0-2ubuntu7.20. Check with dpkg -l nginx or rpm -q nginx and compare against section 2 or the vendor advisory.
I upgraded the package and reloaded. Am I done? No. A reload does not replace the master process, so the old binary keeps running. Run systemctl restart nginx, then confirm that sudo ls -l /proc/$(pgrep -o -x nginx)/exe no longer shows (deleted).
I do not use HTTP/2. Do I still need the update? Yes. The two HTTP/2 flaws do not apply, but the same release fixes eight others in the resolver, HTTP/3, the mail proxy, TLSv1.3 and the stream modules. The urgency differs; the need does not.
Is a server that only serves static files at risk? From CVE-2026-123007, yes. ma.ttias.be says it works against a server that does nothing but serve static files. The only condition is that HTTP/2 is on. CVE-2026-123633 additionally needs proxying to a backend.
I set http2 off. Can the patch wait? It buys time and nothing else. The two HTTP/2 flaws are blocked, eight others are not, and the exposure returns the moment someone turns HTTP/2 back on. Services that rely on gRPC cannot use this step at all.
I am behind a CDN or load balancer. Am I safe? If the front end terminates HTTP/2 and speaks HTTP/1.1 to the origin, Tenable's assessment is that the public proof of concept is unlikely to work. But if the origin IP answers on 443 directly, an attacker does not have to go through the front end. Restrict the origin firewall to the front end's ranges and patch the origin too.
What about Kubernetes ingress? According to a summary of ThreatDefence, F5's NGINX Ingress Controller is fixed in 5.8.0, the community ingress-nginx project was archived in March 2026 and has no fixed release, and setting use-http2: "false" in the controller ConfigMap is the interim step. We saw this in one source summary only, so confirm it against each project's own notices.
I run nginx in Docker. The fixed official images are nginx:1.30.7 and nginx:1.31.9. Move the tag, pull, and recreate the container. For a custom image, update the base image and rebuild. Restarting a container brings the old image straight back.
What about OpenResty, Angie or Tengine? None of the sources we read addressed them. They are built on nginx code, so check each project's security notices. Nothing here supports assuming they are unaffected.
It is not on CISA KEV. Does that make it less urgent? KEV lists flaws after exploitation is confirmed. Absence means exploitation had not been confirmed as of November 19, 2026, not that the flaw is safe. This is an internet-facing web server with a public proof of concept, so there is no reason to wait for a listing. The KEV deadlines bind only US federal civilian agencies in any case; everyone else sets their own order.
8. What remains open and unconfirmed
| Item | Confirmed | Not confirmed |
|---|---|---|
| Open-source fixed versions | 1.30.7 and 1.31.9, four sources agree | The F5 and nginx.org advisories were not opened |
| NGINX Plus | 37.0.8.1 and 37.3.0.1, three sources agree | Whether the affected older branches are R33 or R34 to R36 |
| CVE-2026-123633 range | Affected through 1.31.8 | Whether it starts at 1.19.7 or 1.9.5 |
| Scores | CVSS 4.0 9.2, attributed to F5 by two sources | Who assigned the 8.1 CVSS 3.1 score; NVD scores |
| Distributions | Table as of November 20, 2026, 19:04 UTC | Later status of Fedora, AlmaLinux 8, default Oracle Linux 9, SLES, Leap |
| Exploitation | No reported attacks and not on KEV as of November 19 | Anything since |
| Proof of concept | Rapid7 public code; Censys reproduction as the worker | How the unreleased exploits perform, including under concurrent traffic |
| The other four Xint bugs | Xint says each reaches code execution alone | Censys could not get code execution from three of them |
| Ingress | F5 Ingress Controller 5.8.0, from one source summary | Impact on and alternatives for community ingress-nginx |
| Derivatives | — | OpenResty, Angie, Tengine and other F5 products |
| Kernel SCTP flaw | Reported by Xint; no CVE or patch as of November 19 | Affected kernel range and fix schedule |
| Credit | Xint reported five; several teams reported independently | Who reported CVE-2026-123633 first |
The order of work, once more. Establish exposure from the package version. Move to nginx 1.30.7 or 1.31.9, or to your distribution's fixed package. Restart, do not reload, and check the running binary. Where the upgrade has to wait, turn HTTP/2 off and narrow access to the origin. For any distribution marked unfixed in section 2, read the vendor advisory again.
For why the period before a fix exists is the dangerous one, see "Zero-day explained — why an unpatched flaw is the most expensive thing in security," from August 10, 2026.
Sources
- Tenable — NGINX2Root FAQ: Five vulnerabilities in NGINX (CVE-2026-123007) (2026-11-18, updated 11-19)
- ma.ttias.be — nginx HTTP/2 RCE (CVE-2026-123633, CVE-2026-123007): patch status per distro (2026-11-18; distro table last checked 11-20 19:04 UTC)
- Xint — NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching (2026-11-18)
- ThreatDefence — NGINX CVE-2026-123007 HTTP/2 RCE: Patching and Hunting (2026-11-19)