Security· Security Disclosure

nginx's November 2026 Security Release: 1.30.7 and 1.31.9

nginx 1.30.7 and 1.31.9 fix a critical HTTP/2 RCE (CVE-2026-123007) in every release since 2015 and nine more CVEs, four of them NGINX2Root. Patch and restart.

Atlas Security
Security Advisories
24 min read · 5,185 wordsUpdated November 19, 2026, 8:45 AM CST
Trevor Fannin@trevorfanninFounder, AtlasSecurity alerts and CVE breakdowns, plus infrastructure and general tech.Followon X (opens in a new tab)

Overview

nginx released 1.30.7 (stable) and 1.31.9 (mainline) on November 18, 2026, fixing ten CVEs, and F5, which develops nginx and issues its CVE IDs, published all ten records the same morning. Five are bugs that Xint, the security firm that reported them, groups with a Linux kernel flaw under the name NGINX2Root: use-after-free and memory corruption in HTTP/2, HTTP/3, the DNS resolver, and the mail proxy, each scored CVSS 4.0 9.2 (Critical) by F5. The broadest, CVE-2026-123007 (opens in a new tab), corrupts memory through HTTP/2 flow control and has been in every release since HTTP/2 arrived in nginx 1.9.5 in 2015; nginx rates it "major." A sixth, CVE-2026-118899 (opens in a new tab), can stall a worker on any HTTPS listener with TLS 1.3, which nginx enables by default. F5's verdict on CVE-2026-123007: "An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely."

Why it's urgent: nginx serves 29.7% of the websites whose web server W3Techs can identify, and HTTP/2, all CVE-2026-123007 needs, is on 35.6% of all websites. One of the bug's credited reporters has published proof-of-concept scripts for it, in a GitHub repository created at 5:16 AM CST, before the CVE records went up. The researchers behind NGINX2Root say they used the bug to run commands on a cloud server over its public IP address, then chained an unpatched Linux kernel flaw to take root on the host, from inside a Docker container. See the timeline.

How much traffic it takes: Rapid7 says code execution through CVE-2026-123007 with its published exploit needs about 128 GB of HTTP/2 traffic, which takes roughly two minutes on a 10 Gbit/s link and seventeen at 1 Gbit/s. Links slower than about 300 Mbit/s can't finish before nginx's default one-hour connection limit. That's a real cost, but not a defense: a well-connected attacker covers it in minutes (details).

Key facts

FieldDetail
CVEsTen. The five NGINX2Root CVEs: CVE-2026-123007, "Memory corruption in HTTP/2 flow control"; CVE-2026-123633, "Use-after-free in HTTP/2"; CVE-2026-121810, "Use-after-free in HTTP/3"; CVE-2026-123634, "Use-after-free during response processing in resolver"; CVE-2026-113425, "Use-after-free in mail proxy module." Also CVE-2026-118899, "Infinite loop while reading client request body over TLS 1.3," and four more. Titles are nginx's
Severitynginx rates CVE-2026-123007, CVE-2026-118899, and CVE-2026-113425 "major," and the other NGINX2Root CVEs "medium." F5's CVE records score the five NGINX2Root CVEs CVSS 4.0 9.2 (Critical) and CVSS 3.1 8.1 (High), and CVE-2026-118899 8.7 and 7.5. Red Hat rates CVE-2026-123007 Critical, and Ubuntu gives all five NGINX2Root CVEs High priority. CVE-2026-123007's vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
WeaknessCWE-416, use-after-free (four NGINX2Root CVEs); CWE-191, integer underflow, and CWE-787, out-of-bounds write (CVE-2026-123007); CWE-835, infinite loop (CVE-2026-118899)
ImpactUnauthenticated code execution as the nginx worker's user, and root on the host when chained with an unpatched Linux kernel flaw (how). A stalled worker, from CVE-2026-118899
Fixed innginx 1.30.7 and 1.31.9; NGINX Plus PLS.37.3.0.1 CR and PLS.37.0.8.1 LTS. All November 18, 2026
No official fixnginx 1.29 and older, which nginx calls legacy versions. NGINX Plus R33 through R36, which F5's records list as affected with no fixed version. The Linux kernel flaw, which has neither a CVE nor a patch
ExploitationProof-of-concept scripts for CVE-2026-123007 are public (timeline). Code execution with them takes about 128 GB of HTTP/2 traffic, per Rapid7 (details). None of the ten is in CISA's KEV catalog as of 8:45 AM CST, November 19, 2026
CVE recordsPublished by F5 at 9:23 AM CST (cve.org (opens in a new tab)). NVD lists them as Received, with no NVD scores yet
CreditXint reported all five NGINX2Root bugs. F5's records also credit Rapid7's Stephen Fewer, Wiz Research's Tomer Schwartz, and Ikotas Labs for CVE-2026-123007, and Wiz Research's Nir Ohfeld and Albert Ebb Metnir for CVE-2026-123633. F5's record names F5 as the finder of CVE-2026-118899; nginx's changelog thanks Maxim Dounin. The rest are below

Who is affected

Every nginx below 1.30.7 or 1.31.9 carries some of these bugs. Which ones an attacker can reach depends on how the binary was built and which features its configuration uses (exposure).

Release lineStatus on Nov 18, 2026Fixed inNote
1.31 (mainline)Affected below 1.31.91.31.9All ten CVEs
1.30 (stable)Affected below 1.30.71.30.7Nine; CVE-2026-120993's code isn't in 1.30.x
1.29 and olderAffectedNo fix · legacynginx releases fixes for stable and mainline only
NGINX Plus PLS.37 CRAffected below 37.3.0.1PLS.37.3.0.1Released November 18
NGINX Plus PLS.37 LTSAffected below 37.0.8.1PLS.37.0.8.1Released November 18
NGINX Plus R33–R36AffectedNo fix listedPer F5's CVE records

The oldest vulnerable versions nginx lists are 0.5.33 for the mail proxy bug, 0.6.18 for the resolver bug, and 1.9.5 for HTTP/2 flow control. Xint's report gives different starting points for two of them, 0.5.15 for the mail bug and 1.13.4 for the path it tested in the resolver bug; the ranges here are nginx's. Ubuntu's tracker goes further back for two others, by its own reading of the older code: CVE-2026-123633 on Ubuntu 16.04 through 22.04, and CVE-2026-123640 on 18.04's nginx 1.14.0.

Distribution status

nginx.org packages

FixedTracker
  • Mainline
    Fixed
    1.31.9-1
    Debian, Ubuntu, RHEL, SLES, Amazon Linux 2023, and Alpine repositoriesNov 18
  • Stable
    Fixed
    1.30.7-1
    Same repositoriesNov 18

Ubuntu

HighNo fixTracker
  • 26.10
    Partly fixed
    1.30.4-7ubuntu1.2
    USN-9159-1Nov 18
  • 26.04 LTS
    Partly fixed
    1.28.3-2ubuntu1.13
    USN-9159-1Nov 18
  • 24.04 LTS
    Partly fixed
    1.24.0-2ubuntu7.20
    USN-9159-1Nov 18
  • 22.04 LTS
    Partly fixed
    1.18.0-6ubuntu14.23
    USN-9159-1Nov 18
  • 14.04 – 20.04Through Ubuntu Pro
    Partly fixed
    USN-9159-1Nov 18

Ubuntu gives the five NGINX2Root CVEs High priority, and USN-9159-1 fixes all five wherever they apply. It covers eight of the ten, but not on every release: still open are CVE-2026-125283 everywhere, CVE-2026-123640 on 18.04 through 24.04, and CVE-2026-118899 on 18.04 through 22.04. No release is affected by CVE-2026-120993, since none ships nginx 1.31.4 or later.

Debian

Partly fixedTracker
  • sidUnstable
    Fixed
    1.30.6-4
    Unstable
  • forkyTesting
    Affected
    Not yet migrated
  • 13 "trixie"
    Affected
    No DSA yet
  • 12 "bookworm"LTS
    Affected
    No DLA yet

Debian's tracker now lists all ten. Unstable's 1.30.6-4 fixes the nine that apply to it, and the tracker shows every release as fixed for CVE-2026-120993.

Red Hat

Critical8.1No fixTracker
  • RHEL 10nginx
    Affected
    No RHSA yet
  • RHEL 9nginx, 1.24 and 1.26 streams
    Affected
    No RHSA yet
  • RHEL 8nginx 1.24 stream
    Affected
    No RHSA yet

Red Hat rates CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425 Critical, and CVE-2026-123634 and CVE-2026-118899 Important, and lists RHEL's nginx packages as affected by them. It rates the stream and try_files bugs Moderate and lists them only against Red Hat Hardened Images.

Amazon Linux

Important8.1FixedTracker
  • AL2023nginx
    Fixed
    1.30.7-1.amzn2023.0.1
    ALAS2023-2026-3494Nov 18
  • AL2nginx1 extra
    Fixed
    1.30.7-1.amzn2.0.1
    ALAS2NGINX1-2026-018Nov 19

Both advisories cover nine of the ten; Amazon lists CVE-2026-120993 as not affected. It rates CVE-2026-123007 Important but the mail proxy bug Medium (CVSS 5.9).

Alpine

FixedTracker
  • edge
    Fixed
    1.30.7-r0
    secdbNov 18
  • 3.24
    Fixed
    1.30.7-r0
    secdbNov 18
  • 3.22, 3.23
    Fixed
    1.28.3-r8
    secdbNov 18

The fixed packages cover nine of the ten; 3.22 and 3.23 got the fixes backported to their 1.28.3 packages. Alpine ships stable nginx, which CVE-2026-120993 doesn't affect.

Arch Linux

FixedTracker
  • nginx
    Fixed
    1.30.7-1
    extraNov 18
  • nginx-mainline
    Fixed
    1.31.9-1
    extraNov 18

Fedora

No fixTracker
  • 43, 44, 45
    Affected
    Still on 1.30.6

AlmaLinux

CriticalNo fixTracker
  • 10
    Partly fixed
    1.26.3-16.el10_3.1.alma.2
    ALSA-2026:A024Nov 18
  • 9
    Partly fixed
    1.20.1-32.el9_9.1.alma.3
    ALSA-2026:A025Nov 18
  • 8
    Affected
    No errata yet

AlmaLinux's own advisories, out before any Red Hat fix, cover the two HTTP/2 bugs, CVE-2026-123007 and CVE-2026-123633, in the default nginx packages for 9 and 10.

SUSE

importantPartly fixedTracker
  • openSUSE Tumbleweed
    Fixed
    1.31.9-1.1
    openSUSE-Tumbleweed-2026-12599
  • Enterprise Server 16.1, 16.0, 15 SP7
    In progress
    In progress
  • openSUSE Leap 16.0, 16.1
    Affected
    No fix yet

Oracle Linux

No fixTracker
  • 8, 9, 10
    No information
    No CVE pages yet

NGINX Plus, containers, and other builds

  • NGINX Plus moved to a new release scheme with PLS.37, on an LTS track and a continuous-release (CR) track. The fixes are in PLS.37.3.0.1 CR and PLS.37.0.8.1 LTS. F5's release notes still list R33 through R36 as supported releases, but its CVE records list them as affected with no fixed version.
  • The official Docker images were rebuilt between 11:18 and 11:21 AM CST on November 18. nginx:1.31.9 and nginx:1.30.7 carry the fixes, and stable now points at 1.30.7 on every architecture. As of 8:45 AM CST, November 19, 2026, latest, mainline, and stable-alpine still served the old build on riscv64. Pin the version tag. Pinned digests and older version tags don't move.
  • Images that bundle nginx carry whatever nginx they were built with. As of 8:45 AM CST, November 19, 2026, nginx-proxy's latest and alpine images were last pushed on November 16, and the Dockerfile on its main branch builds from nginx:1.31.6. We haven't checked other projects' images; check each one you run (how).
  • Kubernetes ingress controllers: the Kubernetes project's ingress-nginx is retired. Its README says "Best-effort maintenance will continue until March 2026" and that "Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered," so it gets no fix (end-of-life versions). F5's NGINX Ingress Controller 5.8.0 runs nginx 1.31.9, by our check of its image.
  • Forks that carry nginx's code ship on their own schedules. As of 8:45 AM CST, November 19, 2026, freenginx's newest releases were 1.31.5 and 1.30.2, and OpenResty's was 1.31.8.1, built on nginx 1.31.8. We haven't tested whether they're affected.

How the vulnerabilities work

nginx usually sits at the front of a site: it terminates TLS, speaks HTTP/1.1, HTTP/2, and HTTP/3 to clients, and passes requests on to the applications behind it. Worker processes do the work, each serving thousands of connections at once.

  • What goes wrong. In the five NGINX2Root bugs, nginx keeps using memory it has already freed, or writes past the end of a buffer, while it handles certain connections: HTTP/2 or HTTP/3 traffic, a DNS answer it's waiting on, or a mail login it's checking. In CVE-2026-118899, a worker reading a request body over TLS 1.3 never leaves its read loop and, per F5, "stops accepting new connections and processing existing connections."
  • No login. All ten are reachable by an unauthenticated client over the network. They're in nginx's own connection handling, so they fire before a request reaches the application behind it, and nothing the application checks can stop them.
  • What an attacker gets. Code running as the worker's user, typically www-data or nginx, not root. In our reading, that's still a lot: after TLS termination, a worker sees its connections' traffic in clear text, including other visitors' cookies and credentials, and it holds the site's TLS private keys in memory. Root takes a second bug, like the Linux kernel flaw Xint chained (below).
  • ASLR doesn't settle it. F5's records say code execution is possible "on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR." Luxembourg's CERT, CIRCL, reads the researchers' report more plainly: "Disabling Address Space Layout Randomization (ASLR) is not a prerequisite for the NGINX2ROOT exploits described by the researchers."

CVE-2026-123007: memory corruption in HTTP/2 flow control

HTTP/2 lets each side limit how much data the other may send, through flow-control windows that the peer raises as it reads. nginx's check on those raises didn't count frames it had already queued, so a window could grow past the protocol's limit. In F5's words, the window "can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault."

It's reachable on any listener with HTTP/2 enabled, in every release from 1.9.5 through 1.31.8. The fix is one commit, "HTTP/2: account for queued frames when validating WINDOW_UPDATE," changing eight lines across three files. Turning HTTP/2 off closes this bug and CVE-2026-123633.

How much traffic the public exploit takes

Rapid7, which published the proof of concept for CVE-2026-123007, puts a number on it: "Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data." By its estimate, that's about two minutes on a 10 Gbit/s link and seventeen on a 1 Gbit/s link. nginx closes a connection after an hour by default, so on links slower than about 300 Mbit/s, Rapid7 says, the exploit "will not be able to succeed." It also depends on x86-64 servers with particular CPU features, and on defeating ASLR.

Those are limits of one public exploit, not of the bug, and they don't make HTTP/2 safe to leave on: one well-connected machine moves 128 GB in minutes. They do make an attempt conspicuous. A single HTTP/2 connection pulling in tens of gigabytes while few requests show up in the log is the pattern CIRCL tells investigators to look for (below).

The other NGINX2Root bugs

  • CVE-2026-123633, use-after-free in HTTP/2. It needs HTTP/2 clients, requests proxied to a backend, and a worker "running low on worker_connections," per F5. Vulnerable since 1.19.7. Turning HTTP/2 off closes it.
  • CVE-2026-121810, use-after-free in HTTP/3. The same shape over HTTP/3 (QUIC), vulnerable since HTTP/3 arrived in 1.25.0. F5 adds that "exploitation also depends on conditions beyond the attacker's control."
  • CVE-2026-123634, use-after-free in the resolver. It needs a proxy whose upstream name is built from variables and looked up by nginx's own resolver, plus a subrequest, from mirror or Server Side Includes (SSI), that resolves the same name.
  • CVE-2026-113425, use-after-free in the mail proxy. It needs nginx running as a mail proxy with auth_http, the setting that has an HTTP service approve each login.

CVE-2026-118899: infinite loop over TLS 1.3

F5: "When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body." nginx has enabled TLS 1.3 by default since 1.23.4, so that covers nearly every HTTPS listener on a current nginx. It's a denial of service, not code execution, but each stuck worker stops serving every connection it holds. nginx rates it "major," it's been there since 1.13.0, and F5 lists no workaround. The fix is six lines in two files, covering request bodies over HTTP/1.x and HTTP/3.

Chained with a Linux kernel flaw

Xint also found a use-after-free in the Linux kernel's SCTP code, which CIRCL dates to Linux 4.15 (2018), and chained it with CVE-2026-123007 to get root on the host, including from nginx running in a Docker container. Every container on a host shares its kernel. The flaw has no CVE and no patch yet, and the researchers are "withholding most of the details needed to reproduce or exploit it" until there's a fix.

Two things narrow it. An attacker needs code running on the host first, which the nginx bugs provide; as CIRCL puts it, "A vulnerable NGINX instance does not by itself imply host-root access." And SCTP has to be reachable. Per Xint, "On many Linux distributions, the SCTP module is installed by default and the kernel loads it automatically the first time a program opens an SCTP socket." Blocking that module on hosts that don't use SCTP closes this path (how).

The fixes

Each fix is small. The commits in 1.31.9, by CVE:

Security fixes in nginx 1.31.9
nginx/nginx · release-1.31.8 to release-1.31.9 · Nov 18, 2026
CVE-2026-123007 · HTTP/2e27f5fa
3 files
6 lines added, 2 removed
CVE-2026-123633 · HTTP/22df48a5
1 file
2 lines added, 0 removed
CVE-2026-121810 · QUICb5252da
1 file
4 lines added, 2 removed
CVE-2026-123634 · resolvere39708e
2 commits · 1 file
63 lines added, 8 removed
CVE-2026-113425 · mail754fe68
5 commits · 4 files
103 lines added, 4 removed
CVE-2026-118899 · request body2b129b9
2 commits · 2 files
4 lines added, 2 removed
CVE-2026-123640 · ssl_prereadd9fd14e
2 commits · 1 file
51 lines added, 7 removed
CVE-2026-120993 · PROXY protocolc4892ab
1 file · mainline only
8 lines added, 0 removed
CVE-2026-120967 · stream SSL6f9fcee
1 file
2 lines added, 0 removed
CVE-2026-125283 · try_filesd1ffe6f
1 file
1 lines added, 0 removed

1.30.7 carries the same fixes except CVE-2026-120993's: in our reading of the source at the release tags, the code that fix changes was added in mainline 1.31.4 and never shipped in a 1.30.x release.

Which configurations are exposed

Every unpatched nginx has some of these bugs compiled in. Which ones an attacker can reach depends on the configuration. What follows is our reading of F5's records, nginx's changelog, and Xint's report: exposure, not confirmed exploit paths.

ConfigurationCVEsnginx · F5 CVSS 4.0Off switch
HTTP/2 enabled (http2 on; or listen … http2)CVE-2026-123007; CVE-2026-123633 when proxyingmajor · 9.2; medium · 9.2http2 off;
HTTPS listener with TLS 1.3 (the default)CVE-2026-118899major · 8.7None, per F5
HTTP/3 (listen … quic), proxyingCVE-2026-121810medium · 9.2Remove the quic listeners
proxy_pass with variables, resolver, and mirror or SSICVE-2026-123634medium · 9.2Fixed upstream groups
Mail proxy with auth_httpCVE-2026-113425major · 9.2Trusted networks only
Stream ssl_verify_client on outside the default serverCVE-2026-120967medium · 6.3Also set it in the default server
Stream routing with ssl_prereadCVE-2026-123640minor · 6.9Terminate TLS in nginx
Stream PROXY protocol v2 with dynamic certificates (1.31.4 and later)CVE-2026-120993minor · 6.9PROXY protocol off, or v1
try_files with alias and map regex capturesCVE-2026-125283minor · 6.9Named captures
  • Turning off HTTP/2 isn't enough on its own. Per Xint, it blocks CVE-2026-123007 and CVE-2026-123633 but "does not block the other three nginx vulnerabilities," and it does nothing for the TLS 1.3 loop.
  • The off switches for HTTP/2, HTTP/3, and the resolver come from Xint's report; the rest are F5's. Each has a cost (below).
  • Patch these first: internet-facing HTTPS listeners, which carry the TLS 1.3 loop by default and usually HTTP/2. Then anything with HTTP/3, a mail proxy, or variable upstreams with mirroring. Internal-only listeners come after, though CIRCL counts them reachable "from actors able to reach that listener."

How to check your systems

Check everywhere nginx runs: hosts, containers, ingress controllers, and appliances. A host package check misses containers, and nginx -v misses distribution backports. We tested these commands against the official nginx 1.31.8 and 1.31.9 images, a fixture configuration using every affected feature, Debian's dpkg, AlmaLinux 9's rpm, and Alpine 3.24's apk, with GNU grep 3.8, BusyBox 1.37, procps-ng 4.0.2, and OpenSSL 3.0.

Check the version and the modules

Shell
nginx -vnginx -V 2>&1 | tr ' ' '\n' | grep -E \  '^--with-(http_v2_module|http_v3_module|mail|stream|stream_ssl_preread_module)$'

The first command prints the version of the binary on disk. The second lists which of the affected modules it was built with: no --with-http_v2_module means no HTTP/2 code, and so neither HTTP/2 bug. A distribution's version alone doesn't say whether it's patched (below).

Check which features the configuration uses

Shell
sudo nginx -T 2>/dev/null | sed 's/#.*//' | grep -nE \  -e 'http2|quic|http3' \  -e '^[[:space:]]*(mail|stream)[[:space:]]*\{' \  -e '\b(resolver|mirror|ssi|auth_http|try_files)\b' \  -e '\b(ssl_preread|ssl_verify_client|proxy_protocol)\b'

Match each hit against the exposure table. nginx -T reads the configuration on disk, which can differ from what's loaded until the next reload. Its output can include secrets, so don't paste it anywhere public.

Check for nginx still running an old binary

Shell
ls -l /proc/[0-9]*/exe 2>/dev/null | grep -F 'nginx (deleted)'curl -sI https://example.com | grep -i '^server:'

After an upgrade, the first command lists nginx processes still running the binary the upgrade replaced. In our test, a reload left 1.31.8 serving requests while nginx -v already reported 1.31.9. The second command reads the version a live site reports, unless server_tokens off hides it.

Check distribution packages

Shell
dpkg-query -W -f='${Package} ${Version}\n' 'nginx*'   # Debian, Ubunturpm -q nginx                                          # RHEL, AlmaLinux, Fedoraapk list --installed 'nginx*'                         # Alpine

Compare the full package version with your distribution's advisory, using the board above, not the nginx version.

Check containers and Kubernetes

Shell
docker ps --format '{{.Names}}\t{{.Image}}'docker exec <container> nginx -vdocker run --rm --entrypoint nginx <image> -v

Check every image that bundles nginx, not only nginx itself: a reverse proxy, an ingress controller, or an app image built from an nginx base carries whatever version it was built with. A tag says nothing about the build inside it, and pinned digests never move. For Kubernetes ingress controllers, follow the controller's own advisory (above).

Check the kernel's SCTP exposure

Shell
grep -E '^CONFIG_IP_SCTP=' "/boot/config-$(uname -r)"   # m: module, y: built inlsmod | grep -w sctp                                    # loaded right now?modprobe -n -v sctp                                     # dry run of a load

m means SCTP is a loadable module, which the block below can stop; y means it's built into the kernel, which the block can't. On our Debian 12 test host, SCTP is a module that wasn't loaded, and the dry run printed insmod …/sctp.ko; with the block in place, it prints install /bin/false. Containers share the host's kernel, so run this on the host.

How to fix

Update nginx and restart it

Move to 1.30.7 (stable) or 1.31.9 (mainline). Stable is the conservative choice: 1.31.9 also starts rejecting header lines without a colon and chunked request bodies with too much framing overhead, which can break clients that relied on nginx accepting them. If you skipped October's release, both also carry its four security fixes (CVE-2026-15176, CVE-2026-93479, CVE-2026-95101, and CVE-2026-97629).

  • Packages: your distribution's update (board), or nginx.org's own repositories.
  • Docker: pull nginx:1.31.9, nginx:1.30.7, mainline, or stable, rebuild images built on them, then recreate the containers.
  • NGINX Plus: PLS.37.3.0.1 CR or PLS.37.0.8.1 LTS.

Then restart:

Shell
sudo systemctl restart nginx

Don't stop at a reload. nginx -s reload starts new workers from the binary that's already running. In our test, a reload after swapping in the 1.31.9 binary left the server answering as 1.31.8 until it was restarted. nginx's documented binary upgrade on the fly (opens in a new tab) also works, without dropping connections.

Block the SCTP kernel module

Until there's a kernel fix, Xint recommends blocking the SCTP module on hosts that don't use it: "Until a kernel patch is available, hosts that do not use SCTP can block module loading by placing install sctp /bin/false in a .conf file under /etc/modprobe.d/. This only prevents loading through modprobe. It does not unload a module that is already loaded, and it does not disable SCTP compiled into the kernel." CIRCL gives the same advice, with this command:

Shell
# Only if nothing on the host uses SCTPecho 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.confmodprobe -n -v sctp    # now prints: install /bin/false

Check first that nothing on the host uses SCTP. If lsmod shows the module already loaded, the block takes effect after the module is unloaded or the host reboots.

Check for signs of compromise

A proof of concept is public, so check servers that ran a vulnerable nginx with HTTP/2 open to the internet. CIRCL's guidance: "Investigators should correlate NGINX worker processes spawning unexpected executables, abnormal worker exits/core dumps, unusual long-lived HTTP/2 connections with large inbound traffic but limited logged requests, and unusual outbound connections or DNS activity."

  1. Programs started by workers. A worker has no reason to start one, so any output here is a lead:

    Shell
    for w in $(pgrep -f 'nginx: worker'); do pgrep -a -P "$w"; done

    It only shows what's running now. Xint's write-up includes an auditd rule that records new ones going forward.

  2. Worker crashes. A failed attempt can crash a worker, which nginx logs at the alert level:

    Shell
    sudo grep -E 'worker process [0-9]+ exited on signal' /var/log/nginx/error.logdocker logs <container> 2>&1 | grep 'exited on signal'

    We captured the real line by crashing a worker in the official image: [alert] 1#1: worker process 30 exited on signal 11. Workers crash for other reasons too, and CERT-EU calls a crash "not a high-fidelity indicator of successful remote code execution but rather an indication of exploitation attempts," so weigh it with the rest.

If anything turns up, isolate the server, preserve its logs, and report it (IC3 in the US). Treat the TLS private keys and any credentials the workers could reach as exposed: reissue the certificates and rotate the credentials.

If you can't patch immediately

CERT-EU "recommends updating vulnerable instance as soon as possible, prioritising internet-facing devices," and says turning off HTTP/2 on exposed listeners mitigates CVE-2026-123007 and CVE-2026-123633 until then. CIRCL's guidance: "Organisations operating NGINX for public websites, reverse proxies, APIs, load balancers, Kubernetes ingress, mail gateways or third-party appliances should inventory actual deployed NGINX binaries and configurations, confirm HTTP/2/HTTP/3 and upstream reachability, and urgently arrange updates or temporary feature isolation. Prioritize Internet-facing services and NGINX deployments with sensitive upstream access."

  • HTTP/2 (CVE-2026-123007, CVE-2026-123633): set http2 off; in every server block on the port (1.25.1 and later), or remove http2 from the listen lines (older versions). Clients fall back to HTTP/1.1, and anything that requires HTTP/2, such as native gRPC, breaks. Confirm from outside the network:

    Shell
    openssl s_client -connect example.com:443 -servername example.com -alpn h2 \  </dev/null 2>&1 | grep -E 'ALPN protocol|No ALPN negotiated'

    No ALPN negotiated means HTTP/2 is off on that port; ALPN protocol: h2 means it's still on.

  • HTTP/3 (CVE-2026-121810): remove the listen … quic lines, set http3 off;, and replace any Alt-Svc header that advertises HTTP/3 with Alt-Svc 'clear'. Clients fall back to TCP.

  • Resolver (CVE-2026-123634): point proxy_pass at a fixed upstream group instead of a name built from variables, and avoid mirror and SSI there. The reporters found that mirror_request_body on stopped their exploit, "but it does not fix the resolver bug."

  • Mail proxy (CVE-2026-113425): bind the mail listeners to loopback, or let only trusted IP addresses reach them.

  • Stream and try_files: F5's switches are in the exposure table.

  • Behind a CDN: CIRCL notes that a CDN speaking HTTP/2 to visitors and HTTP/1.1 to the origin keeps CVE-2026-123007 away from the origin, as long as attackers can't reach the origin directly.

A reload applies these changes only to new connections. HTTP/2 and mail sessions that are already open stay on the old workers until they close; restarting cuts them off, at the cost of dropping every open connection.

End-of-life versions

nginx releases fixes for two branches at a time, stable and mainline, and nginx.org lists everything older under "Legacy versions." Every legacy release back to 1.9.5 that has HTTP/2 carries CVE-2026-123007, and the mail and resolver bugs go back to 0.5.33 and 0.6.18. On those versions, the only fixes are distribution backports. Debian 12 ships 1.22.1, Ubuntu 22.04 and 24.04 ship 1.18.0 and 1.24.0, and AlmaLinux 9 ships 1.20.1, each patched under its own package version (board).

NGINX Plus switched to PLS.37's LTS and CR tracks, and F5 supports each LTS version for three years. Each older R release gets 24 months of support from its release date, per F5's release notes, and the CVE records list R33 through R36 as affected with no fixed version. R33, released November 19, 2024, reaches the end of its 24 months tomorrow, November 19, 2026.

Kubernetes' ingress-nginx is in the same position as a legacy branch. Its maintainers stopped best-effort maintenance in March 2026 and promise "no updates to resolve any security vulnerabilities that may be discovered," so clusters still running it won't get these fixes. Moving to a maintained controller is the only remedy.

Timeline and exploitation status

All times are US Central: CST (UTC−6). Xint gives dates only, in UTC.

  • Fix
  • Advisory or rating
  • Exploit or proof of concept
  1. Nov 19
    1. Amazon Linux 2's nginx1 package is fixed (ALAS2NGINX1-2026-018)

  2. Nov 18
    1. 11:21 PMUbuntu publishes USN-9159-1, fixing eight of the ten CVEs on most releases

    2. 7:15–7:35 PMAlpine's backported fixes for 3.23 and 3.22 reach its mirrors

    3. 4:56 PMF5 updates CVE-2026-120993's record, dropping stable 1.30.6 from the affected versions

    4. AlmaLinux 9 and 10 ship fixes for the two HTTP/2 bugs

    5. Amazon Linux 2023 ships nginx 1.30.7 (ALAS2023-2026-3494)

    6. CERT-EU publishes advisory 2026-022 (opens in a new tab)

    7. 11:18–11:21 AMDocker's official nginx images are rebuilt with 1.30.7 and 1.31.9

    8. 11:14–11:16 AMAlpine's fixed 1.30.7-r0 packages for edge and 3.24 reach its mirrors

    9. 11:08 AMArch Linux ships nginx 1.30.7-1

    10. 10:56 AMArch Linux ships nginx-mainline 1.31.9-1

    11. By 10:51 AMRed Hat rates CVE-2026-123007 Critical

    12. 10:40–10:45 AMMore repositories claiming proofs of concept for other CVEs in the release appear; some describe a different bug than the CVE they name

    13. Xint publishes NGINX2Root (opens in a new tab), and CIRCL publishes TR-105 (opens in a new tab)

    14. 9:54 AMnginx publishes its GitHub release of 1.31.9

    15. 9:23 AMF5 publishes the ten CVE records

    16. 9:13 AMWiz Research publishes its write-up (opens in a new tab) of the two HTTP/2 bugs

    17. 8:00 AMRapid7 publishes its analysis (opens in a new tab), saying code execution takes about 128 GB of HTTP/2 traffic

    18. 5:16 AMA GitHub repository of proof-of-concept scripts for CVE-2026-123007 is created by Rapid7's Stephen Fewer, one of its credited reporters

  3. Nov 10
    1. Xint finishes validating nginx's patches

  4. Oct 27
    1. The reports reach F5's nginx development team

  5. Oct 16
    1. Xint reports them to F5 through HackerOne

  6. Oct 11
    1. Xint finds the nginx bugs

Only the first repository comes from a credited reporter; the others appeared within hours, and not all of them match the bugs they claim. None of the ten is in CISA's Known Exploited Vulnerabilities catalog as of 8:45 AM CST, November 19, 2026. We haven't tested any public proof of concept, and we aren't linking them.

Other vulnerabilities fixed in this release

CVESeverity (nginx · F5 CVSS 4.0)TitleLines
CVE-2026-120967medium · 6.3SNI bypass when using client certificate validation in stream+2 −0
CVE-2026-123640minor · 6.9Insufficient validation in stream ssl_preread module+51 −7
CVE-2026-125283minor · 6.9Buffer overflow when using alias with try_files+1 −0
CVE-2026-120993minor · 6.9NULL pointer dereference when using PROXY protocol version 2+8 −0
  • Credit, per F5's records: CERT.PL (CVE-2026-120967); Vivek Parikh of BreachX Zero Day Labs (CVE-2026-123640); Marc Luchian and Liviu-Alexandru Bud (CVE-2026-125283); and ruokeqx (CVE-2026-120993).
  • CVE-2026-120993's range: nginx lists mainline 1.31.4 through 1.31.8 only, and since the evening of November 18, so does F5's record. It first listed stable 1.30.6 too, though the function the fix changes isn't in any 1.30.x release, in our reading of the source and in Ubuntu's.
  • Without a CVE, 1.31.9 also fixes a buffer overflow when a GeoIP database in the MMDB format contains invalid coordinates.

Updates to this post

We'll revise this post and mark it updated when any of these change: a CISA KEV listing or reports of exploitation; NVD scores; fixes from the distributions on the board; a CVE or a kernel fix for the SCTP flaw; fixes for NGINX Plus R33 through R36, ingress controllers, or images and projects that bundle nginx; and changes to F5's CVE records.

  1. Latest

    Added Rapid7's estimate that code execution with its published exploit takes about 128 GB of HTTP/2 traffic, and CERT-EU's advisory. Ubuntu (USN-9159-1, which still leaves CVE-2026-125283 open everywhere and two others on older releases), Amazon Linux 2023 and 2, Alpine 3.22 and 3.23, and openSUSE Tumbleweed shipped fixes; AlmaLinux 9 and 10 fixed the two HTTP/2 bugs; Debian fixed unstable and now tracks all ten. Red Hat rated the rest of the NGINX2Root CVEs, three Critical and one Important, with no fixes yet. Docker's stable tag now covers every architecture. F5 corrected its CVE-2026-120993 record, which no longer lists stable 1.30.6. Unchanged: KEV, NVD's status, Fedora, Oracle, nginx-proxy, freenginx, OpenResty, and NGINX Plus R33 through R36.

Get help

nginx reports its version in the Server header unless it's told not to, and tells any client whether it speaks HTTP/2 or HTTP/3. Our free security audit checks the domains and public IPs you verify for exposed services, publicly visible software versions with known CVEs, TLS, email security, DNS, and HTTP headers.

Atlas Service
Free Security Audit
Non-destructive checks of your verified domains and public IPs, and a PDF report with every finding ranked and a fix for each, within 3 business days of verification.

Also published today: Vite's dev-server RCE, GHSA-p4f5-76q4-ffq7.

Sources

nginx

F5

CVE records

Researchers and agencies

Distributions

Containers and downstream projects

Usage

Atlas Security
Security Advisories

The Atlas security byline: write-ups of vulnerabilities in widely deployed software — what changed, who is exposed, and what to check — verified against primary sources.

Continue reading

More from the Atlas Meridian

Security
13 min read

APT's November 2026 Download Verification Bypass: CVE-2026-109518

An APT flaw lets an on-path attacker swap a verified package and run code as root on Debian, Ubuntu, and derivatives. Debian and Ubuntu have fixes out.

Atlas Security
Security Advisories
View category
Security
26 min read

PHP's October 2026 Critical RCEs: CVE-2026-109618 and CVE-2026-109619

PHP fixed two critical unauthenticated RCEs in 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Attackers chain them with a Linux kernel bug to get root: patch both now.

Atlas Security
Security Advisories
View category
Security
29 min read

Google Brotli's October 2026 Decoder RCE: CVE-2026-111497

CVE-2026-111497 (Node2Shell) is a CVSS 9.2 RCE in Google's Brotli decoder, now in CISA's KEV. Fixed in Brotli 1.2.1 and Node.js 22.23.4, 24.22.1, and 26.12.1.

Atlas Security
Security Advisories
View category
Engage · Atlas Engineering

Reading is one thing. Shipping is another.

If this writeup resonates with what you're building, let's talk. We'll connect you directly with an engineer to assist.