Summary

FieldDetail
Releasesnginx 1.30.7 (stable) and 1.31.9 (mainline), both released 2026-11-18
AdvisoriesTen nginx CVEs, listed under Advisories; nine are fixed in both releases, and the tenth affected mainline only
HeadlineCVE-2026-123007 — memory corruption in HTTP/2 flow control, reachable by an unauthenticated remote client on any server with HTTP/2 enabled
NicknameNGINX2Root — Xint’s name for five of the ten: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425
Highest severityThose five: 8.1 high (CVSS 3.1) / 9.2 critical (CVSS 4.0), scored by F5 as CNA; nginx.org rates CVE-2026-123007, CVE-2026-118899, and CVE-2026-113425 “major”
TypesMemory corruption and four use-after-frees that F5 says can lead to code execution, a denial-of-service loop, a worker crash or two, and two access-control bypasses in the stream module
Who is exposedAny nginx serving HTTP/2, for the headline bug. The others need a specific feature — see Detection
KEV listedno
Public exploitnone published — Xint and Wiz Research each say they have a working exploit and are withholding it. CISA’s SSVC assessment on all ten CVE records says exploitation none
EPSSnot yet scored

This is the second nginx security release in five weeks. A host updated for October’s CVE-2026-97205 tracker — to 1.30.6 or 1.31.7 — is vulnerable again: to nine of these on stable, and to all ten on mainline.

Advisories

nginx.org publishes the vulnerable ranges; F5, which is the CNA, publishes the scores and its own advisory per CVE. The ranges below are nginx.org’s; F5’s agree except where noted under Naming differences.

CVEnginx.org titleVulnerableCWECVSS 3.1 / 4.0F5 advisory
CVE-2026-123007Memory corruption in HTTP/2 flow control1.9.5 – 1.31.8CWE-191, CWE-7878.1 / 9.2K000163926
CVE-2026-123633Use-after-free in HTTP/21.19.7 – 1.31.8CWE-4168.1 / 9.2K000163928
CVE-2026-121810Use-after-free in HTTP/31.25.0 – 1.31.8CWE-4168.1 / 9.2K000163927
CVE-2026-123634Use-after-free during response processing in resolver0.6.18 – 1.31.8CWE-4168.1 / 9.2K000163925
CVE-2026-113425Use-after-free in mail proxy module0.5.33 – 1.31.8CWE-4168.1 / 9.2K000163931
CVE-2026-118899Infinite loop while reading client request body over TLS 1.31.13.0 – 1.31.8CWE-8357.5 / 8.7K000163930
CVE-2026-125283Buffer overflow when using alias with try_files0.9.6 – 1.31.8CWE-1915.3 / 6.9K000163933
CVE-2026-123640Insufficient validation in stream ssl_preread module1.15.2 – 1.31.8CWE-12895.3 / 6.9K000163935
CVE-2026-120967SNI bypass when using client certificate validation in stream1.25.5 – 1.31.8CWE-12894.8 / 6.3K000163934
CVE-2026-120993NULL pointer dereference when using PROXY protocol version 21.31.4 – 1.31.8CWE-4765.3 / 6.9K000163932

Not vulnerable: 1.31.9+ and 1.30.7+. CVE-2026-120993 is the exception to “both releases”: the code it affects exists only in mainline, from 1.31.4, so its fix is in 1.31.9 alone and the stable track never had the bug.

What each bug needs

  • CVE-2026-123007 — HTTP/2 enabled on a listener. F5 names no other condition, and Wiz reports reaching it on a server of plain static files. The flow-control window can be pushed past its limit, which overflows a heap buffer — a worker crash, and code execution where ASLR is disabled or bypassed.
  • CVE-2026-123633 — HTTP/2 for client connections, requests proxied to a backend, and a worker running short of worker_connections. A use-after-free in the worker with the same impact.
  • CVE-2026-121810 — HTTP/3 (listen … quic), again with the worker short of worker_connections; Xint adds that the requests are forwarded to a backend. A use-after-free; F5 notes that exploitation depends on conditions outside the attacker’s control.
  • CVE-2026-123634 — a resolver, a proxy_pass whose server name contains variables, and an SSI or mirror subrequest to a location that resolves the same name. A use-after-free in the worker.
  • CVE-2026-113425 — the mail proxy (a mail block). F5 says no more than that; Xint narrows it to proxy on with auth_http, and says the attacker needs no valid credentials. A use-after-free during a mail session.
  • CVE-2026-118899 — a listen … ssl server in the http block with TLS 1.3 enabled. That is the default from nginx 1.23.4; older series need TLSv1.3 named in ssl_protocols. A crafted TLS connection makes the worker loop forever while reading a request body; that worker stops serving all its connections.
  • CVE-2026-125283 — try_files and alias together with a map variable, where regex captures in the map and in try_files combine badly. A worker crash.
  • CVE-2026-123640 — ssl_preread on in the stream module. A crafted ClientHello makes the $ssl_preread_* variables say something other than what the backend’s TLS stack will see, so a connection can be routed to a backend that should be unreachable.
  • CVE-2026-120967 — ssl_verify_client on in a stream server that is not the default server of its listening socket. The certificate is checked against the default server’s settings, so client-certificate verification can be bypassed.
  • CVE-2026-120993 — mainline only: stream SSL with certificates loaded dynamically (variables in ssl_certificate) and proxy_protocol version 2 to the backend. An abbreviated TLS handshake crashes the worker. Builds against BoringSSL or AWS-LC are not affected.

NGINX2Root

Xint published five of the ten under the name NGINX2Root on the day of the release, and Wiz Research published the two HTTP/2 bugs separately the same day. What the write-ups add to the advisories:

  • Both teams report working exploits for CVE-2026-123007 — Wiz on official nginx 1.31.7 and 1.31.8 builds — and both are withholding them. Neither reports attacks in the wild.
  • Several finders, independently. F5 credits Rapid7, Wiz Research, Xint, and Ikotas Labs for CVE-2026-123007, and Metnir, Wiz Research, and Xint for CVE-2026-123633. The nginx changelog thanks Xint alone for the first and “Albert of Vexera AI” for the second. Wiz reported CVE-2026-123007 on 2026-11-16, two days before the release, which already contained the fix.
  • Timeline. Xint dates its findings to 2026-10-11 and its report to F5 to 2026-10-16; the fixes were committed to nginx on 2026-11-11 and released a week later.
  • Two first-affected versions differ. Xint gives 1.13.4 for the resolver bug and 0.5.15 for the mail proxy bug, as the first releases affected in the configurations it tested; nginx.org and F5 say 0.6.18 and 0.5.33. The table above uses nginx.org’s.

Xint counts a sixth vulnerability under the name: a separate Linux kernel bug, with no CVE listed. It is not an nginx bug and this tracker does not follow it.

Naming differences

F5’s advisory titles name these by module rather than by bug. Two could mislead:

  • CVE-2026-125283 is “NGINX map directive and regex matching vulnerability” at F5 — the same title F5 gave October’s CVE-2026-93479 and close to July’s CVE-2026-42533. It is a different bug from both; nginx.org calls it a buffer overflow when using alias with try_files.
  • CVE-2026-120967 and CVE-2026-120993 are both “NGINX ngx_stream_ssl_module vulnerability” at F5. The first is the client-certificate bypass; the second is the mainline-only crash.

F5’s advisory and the CVE record for CVE-2026-120993 list nginx 1.30.6 as vulnerable and 1.30.7 as its fix. nginx.org lists mainline only, the 1.30.7 changelog has no entry for it, and the commits between 1.30.6 and 1.30.7 do not include the fix that 1.31.9 carries. This tracker follows nginx.org.

F5’s advisory for CVE-2026-118899 lists only 1.13.0 for NGINX Open Source, with no fixed release. nginx.org gives 1.13.0 – 1.31.8, fixed in both releases, and both changelogs list the fix.

Other F5 products

F5 announced these together with twelve BIG-IP vulnerabilities, which this tracker does not follow (K000164058 is the index). Closer to home, F5 lists the products that bundle the nginx core as affected by CVE-2026-118899 and as needing their own updates: NGINX Ingress Controller, NGINX Gateway Fabric, NGINX Instance Manager, and the WAF and DoS products for NGINX. NGINX Plus is affected by all ten; its fixed releases are in F5’s advisories.

Patch status

A row is Fixed once its nginx carries the fix for every one of these CVEs that applies to its version — a release at or past 1.30.7 (stable) or 1.31.9 (mainline), or a distribution package with the patches backported. Older series are outside some of the ranges: 1.26 is affected by nine of the ten, and 1.22 by seven — it predates HTTP/3 and the stream client-certificate bug. A package with only some of the fixes stays vulnerable.

Current version is what the release ships today; First fixed is the first build that carried the fixes, and Fixed since the date it became available.

DistributionReleaseCurrent versionFirst fixedFixed sinceStatus
nginxmainline1.31.91.31.92026-11-18✅ Fixed
nginxstable1.30.71.30.72026-11-18✅ Fixed
Debiansid (unstable)1.30.6-41.30.6-42026-11-18✅ Fixed
Debianforky (testing)1.30.6-3——❌ Vulnerable
Debian13 (trixie)1.26.3-3+deb13u111.26.3-3+deb13u112026-11-19✅ Fixed
Debian12 (bookworm)1.22.1-9+deb12u111.22.1-9+deb12u112026-11-19✅ Fixed
pkgsrcpkgsrc-current — nginxnginx-1.30.7nginx-1.30.72026-11-18✅ Fixed
pkgsrcpkgsrc-current — nginx-develnginx-devel-1.31.9nginx-devel-1.31.92026-11-19✅ Fixed
pkgsrcpkgsrc-2026Q3 — nginxnginx-1.30.7nginx-1.30.72026-11-19✅ Fixed
pkgsrcpkgsrc-2026Q3 — nginx-develnginx-devel-1.31.5——❌ Vulnerable — needs 1.31.9
NixOSnixos-unstable — nginxStable1.30.71.30.72026-11-20✅ Fixed
NixOSnixos-unstable — nginxMainline1.31.91.31.92026-11-20✅ Fixed
NixOSnixos-unstable-small — nginxStable1.30.71.30.72026-11-18✅ Fixed
NixOSnixos-unstable-small — nginxMainline1.31.91.31.92026-11-18✅ Fixed
NixOSnixos-26.05 — nginxStable1.30.71.30.72026-11-19✅ Fixed
NixOSnixos-26.05 — nginxMainline1.31.91.31.92026-11-19✅ Fixed
NixOSnixos-26.05-small — nginxStable1.30.71.30.72026-11-18✅ Fixed
NixOSnixos-26.05-small — nginxMainline1.31.91.31.92026-11-18✅ Fixed
nixpkgsmaster — nginxStable1.30.71.30.72026-11-18✅ Fixed
nixpkgsmaster — nginxMainline1.31.91.31.92026-11-18✅ Fixed
nixpkgsrelease-26.05 — nginxStable1.30.71.30.72026-11-18✅ Fixed
nixpkgsrelease-26.05 — nginxMainline1.31.91.31.92026-11-18✅ Fixed
nixpkgsnixpkgs-unstable — nginxStable1.30.71.30.72026-11-20✅ Fixed
nixpkgsnixpkgs-unstable — nginxMainline1.31.91.31.92026-11-20✅ Fixed

nginx

nginx ships two supported tracks: stable (1.30.x), the one most distributions package, and mainline (1.31.x), where new features land first. Both got their fixed release on the same day, and every older series is past its end of support upstream — a host on 1.28 or earlier gets no further nginx.org release and has to move to 1.30.7 or rely on its distribution’s backports.

1.30.7’s changelog lists only the security fixes. 1.31.9 also carries ordinary bug fixes and two behaviour changes: header lines without a colon are now rejected, and so is a chunked request body with too much framing overhead.

For operators building from source, nginx.org publishes no separate patches; the fixes ship in the 1.30.7 and 1.31.9 tarballs.

Debian

The Debian security tracker is the authoritative source for per-suite status. sid’s 1.30.6-4 upload fixes all nine CVEs that apply to Debian’s 1.30/1.26/1.22 builds — CVE-2026-120993 is mainline-only and does not apply to Debian. DSA-6642-1 and DLA-4918-1 carry the same nine fixes to trixie and bookworm respectively; bookworm needs only seven of them, lacking HTTP/3 and the stream client-certificate code the other two patch. forky has no upload yet and remains vulnerable to all nine.

Debian packages the stable track only, and the nginx source package also builds the libnginx-mod-* dynamic modules, so one row per suite covers them all.

Debian 11 (bullseye) left Debian LTS on 2026-08-31. Its nginx 1.18 is inside most of these ranges, CVE-2026-123007 included, and no Debian fix is coming — a host still on bullseye needs to upgrade to a supported release, a paid extended-support offering such as Freexian ELTS, or the configuration mitigations below.

pkgsrc

The pkgsrc tree (NetBSD’s package collection, also used on SmartOS, macOS via pkgin, and elsewhere) ships the two tracks as separate packages: www/nginx follows stable and www/nginx-devel follows mainline. pkgsrc-2026Q3, the current quarterly branch, receives fixes by pull-up from pkgsrc-current.

pkgsrc-current carries both fixes: www/nginx picked up 1.30.7 on 2026-11-18 and www/nginx-devel 1.31.9 on 2026-11-19. pkgsrc-2026Q3 pulled up www/nginx to 1.30.7 the same day; its www/nginx-devel is still at 1.31.5, which also predates October’s fixes.

The identifier carries an nbN suffix when the package’s PKGREVISION is set. That revision bumps for many reasons besides security patches — recursive bumps for shared-library ABI changes, dependency and build-system tweaks — so an nbN suffix on its own says nothing about these CVEs.

NixOS

nixpkgs builds both tracks: nginxStable (also plain nginx, and the NixOS services.nginx module’s default package) and nginxMainline. Variants such as nginxShibboleth and builds with extra modules from nginxModules derive from one of these two, so the two rows per channel cover them.

nixpkgs-unstable is the channel for Nix users outside NixOS — on macOS or another Linux distribution. A channel row’s Fixed since is the date that channel published its first release containing the fix; a branch row’s is the date the fix was merged into that branch.

The fix landed on master and on release-26.05 within hours of the release. Each branch’s lighter -small gate — nixos-unstable-small and nixos-26.05-small — published a release carrying it the same day, and nixos-26.05 followed the next day. nixos-unstable, the one channel with the full (non--small) Hydra gate on the fast-moving branch, and nixpkgs-unstable both took two days longer.

Flake users

A flake input such as github:NixOS/nixpkgs/nixos-unstable follows the branch of that name, which moves with the channel — so the channel’s row answers for it. An input on master or release-26.05 gets the fix as soon as it lands there, before any channel publishes it.

Detection

First check the version. A build at or past 1.30.7 or 1.31.9 is fixed; a distribution build is fixed only once the table above says so — a distribution backports fixes without changing the version nginx -v prints, so compare the full package version.

nginx -v

Next check which features a host uses. Run the checks against the full configuration that nginx -T prints — it follows every include. Run them as root, or with sudo. A grep only finds candidates: read the surrounding blocks to see whether the directives actually apply to the same requests.

CVE-2026-123007 and CVE-2026-123633 need HTTP/2. Any hit here is exposure to the first; the second also needs the requests proxied:

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])(listen[[:space:]][^;]*[[:space:]]http2|http2[[:space:]]+on)'

To see what a server actually negotiates, ask it from outside — and ask the nginx host itself where a CDN sits in front. ALPN protocol: h2 in the output means HTTP/2 is on:

openssl s_client -connect www.example.com:443 -alpn h2 </dev/null 2>/dev/null | grep ALPN

CVE-2026-121810 needs HTTP/3:

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])listen[[:space:]][^;]*[[:space:]]quic'

CVE-2026-118899 needs TLS 1.3 on an http listener. From nginx 1.23.4 every listen … ssl server is exposed unless an ssl_protocols line that applies to it leaves out TLSv1.3; before that, only where an ssl_protocols line names it:

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])(listen[[:space:]][^;]*[[:space:]]ssl|ssl_protocols[[:space:]])'

CVE-2026-123634 needs a resolver, a proxy_pass with a variable in the server name, and SSI or mirror:

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])(resolver|mirror|ssi)[[:space:]]|(^|[[:space:]{;])proxy_pass[[:space:]][^;]*[$]'

CVE-2026-113425 needs the mail proxy. Most hosts have no mail block at all:

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])(mail[[:space:]]*[{]|auth_http[[:space:]])'

CVE-2026-125283 needs alias and try_files used together, with a regex map:

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])(alias|try_files|map)[[:space:]]'

The three stream-module bugs need ssl_preread (CVE-2026-123640), ssl_verify_client (CVE-2026-120967), or proxy_protocol with dynamic certificates on mainline (CVE-2026-120993):

nginx -T 2>/dev/null | grep -nE '(^|[[:space:]{;])(ssl_preread|ssl_verify_client|proxy_protocol)[[:space:]]'

Signs of an attack

Xint warns that an attack on the HTTP/2 bug may leave little in the access log, and Wiz calls the following general warning signs, not confirmed indicators. Workers that die unexpectedly are the first thing to look for:

grep -Ei 'worker process.*exited on signal|segfault' /var/log/nginx/error.log

Both write-ups also point at long-lived HTTP/2 connections sending unusually large amounts of data, and at processes started by an nginx worker — which a web server normally never does.

Mitigation

The real fix is nginx 1.30.7 / 1.31.9, or a distribution package with the patches. Until one is installed, these workarounds close individual bugs. F5 lists none for the HTTP/2, HTTP/3, and TLS 1.3 bugs: turning HTTP/2 off is Xint’s and Wiz’s advice, and turning HTTP/3 off is Xint’s.

  • CVE-2026-123007, CVE-2026-123633 — turn HTTP/2 off: from nginx 1.25.1, http2 off; in each affected server block, and remove http2 from every listen line; before 1.25.1, the listen parameter is the only switch. Clients fall back to HTTP/1.1, but anything that requires HTTP/2 — native gRPC, for one — stops working.
  • CVE-2026-121810 — remove the quic listeners and stop advertising HTTP/3 in Alt-Svc.
  • CVE-2026-123634 — proxy to a fixed upstream rather than a server name built from variables, and drop SSI or mirror where they are not needed. Xint found that mirror_request_body on stopped its exploit but does not fix the bug, and says not to rely on it.
  • CVE-2026-113425 — restrict the mail listeners to trusted networks.
  • CVE-2026-118899 — no workaround from F5, or from anyone else. Leaving TLSv1.3 out of ssl_protocols removes the condition F5 names, at the cost of TLS 1.3.
  • CVE-2026-125283 — use named captures ((?<name>…)) instead of $1-style ones, and do not reuse a capture variable in another regex match.
  • CVE-2026-123640 — terminate TLS in nginx (listen … ssl and $ssl_server_name) instead of routing on ssl_preread.
  • CVE-2026-120967 — set ssl_verify_client on in the default server of the shared listening socket, or give the server that requires client certificates its own address and port.
  • CVE-2026-120993 — set proxy_protocol off or plain proxy_protocol on (version 1), or turn off abbreviated handshakes with ssl_session_tickets off and ssl_session_cache off.

Apply a change with nginx -t && nginx -s reload, then make sure the old workers have gone: a reload leaves them serving their open connections, and a long-lived HTTP/2 connection can keep one alive. Restarting nginx drops them at once.

A workaround does not change a row’s status above: only an nginx build with the fixes does.

Verification log

Every verdict in the table above is backed by a checkable source. This log records the provenance — the advisory, repository index, or git reference that established each fact — so any row can be audited or reproduced. Most readers never need it.

Full verification log

Upstream

  • nginx.org (security advisories, CHANGES, CHANGES-1.30):
    • Nine CVEs: not vulnerable 1.31.9+ and 1.30.7+. CVE-2026-120993: not vulnerable 1.31.9+, vulnerable 1.31.4 – 1.31.8. Vulnerable ranges and titles as in the Advisories table.
    • Severity “major” for CVE-2026-123007, CVE-2026-118899, and CVE-2026-113425; “medium” for CVE-2026-123634, CVE-2026-121810, CVE-2026-123633, and CVE-2026-120967; “minor” for the other three.
    • The Changes with nginx 1.31.9 and Changes with nginx 1.30.7 headers are both dated 18 Nov 2026, the Fixed since of the two nginx rows. The 1.30.7 entry has nine Security lines and nothing else; 1.31.9’s has ten.
    • Current version is the newest Changes with nginx header of each changelog.
  • nginx source (github.com/nginx/nginx, tags release-1.30.6 to release-1.30.7 and release-1.31.8 to release-1.31.9):
    • The security fixes were committed on 2026-11-11 on both branches; b89c4100bf67 (“HTTP/2: account for queued frames when validating WINDOW_UPDATE”) is the CVE-2026-123007 fix on stable.
    • c4892abca630 (“Core: fixed segfault in PROXY protocol v2 with dynamic certificates”) is in 1.31.9 and has no counterpart between 1.30.6 and 1.30.7.
  • F5 advisories (K000163925 – K000163928 and K000163930 – K000163935; F5’s portal needs JavaScript, so read as rendered by a headless browser on 2026-11-18):
    • All published 2026-11-18. CWE, both CVSS scores, F5’s trigger conditions, mitigations, and acknowledgements in this tracker are from these.
    • K000163932 lists NGINX Open Source 1.30.6 as vulnerable to CVE-2026-120993 and 1.30.7 as the fix; K000163930 lists only 1.13.0 for CVE-2026-118899. See Naming differences.
  • CVE records (the CVE Services API, F5 as CNA):
    • All ten published 2026-11-18; CVSS 3.1 and 4.0 scores match F5’s advisories. The CVE-2026-123007 record adds CWE-787.
    • CISA’s SSVC is recorded on all ten records: exploitation none on every one.
    • NVD’s status for CVE-2026-123007 is “Analyzed”, with its listed CVSS v3.1/v4.0 scores marked “Secondary” and sourced to F5 — no NVD score of its own.
    • None is in CISA’s KEV catalog (release of 2026-11-17, the latest at seed); FIRST has no EPSS score for any of them yet.
  • Write-ups (Xint, Wiz Research, both dated 2026-11-18): the NGINX2Root name and its five CVEs, the exploit and in-the-wild statements, the timeline, the HTTP/2 and HTTP/3 workarounds, the attack signs, and the conditions credited to Xint or Wiz in What each bug needs are theirs.

Distributions

  • Debian (security tracker per-CVE pages and JSON; versions from scripts/debian-versions):
    • All nine applicable CVEs show src:nginx fixed in sid at 1.30.6-4, in trixie-security via DSA-6642-1, and in bookworm-security via DLA-4918-1 (bookworm’s DLA covers only the seven that apply to 1.22); forky is listed vulnerable to all nine, with no upload yet.
    • sid’s Fixed since is 1.30.6-4’s first_seen on snapshot.debian.org, 2026-11-18.
    • trixie’s and bookworm’s Fixed since are their DSA/DLA upload’s first_seen on snapshot.debian.org, both 2026-11-19.
    • Current version is the -security archive’s where it is ahead of the main archive.
  • pkgsrc (local clone, scripts/pkgsrc-versions):
    • www/nginx and www/nginx-devel on origin/trunk and origin/pkgsrc-2026Q3; no patch names a tracked CVE.
    • www/nginx-devel sets PKGNAME, so its identifier reads nginx-devel-<version>.
    • pkgsrc-current’s www/nginx picked up 1.30.7 in 987334bcbb56 (“nginx: Update to 1.30.7”) on origin/trunk.
    • pkgsrc-current’s www/nginx-devel picked up 1.31.9 in 19a7db53ed3d (“www/nginx-devel: Update to 1.31.9”) on 2026-11-19.
    • pkgsrc-2026Q3’s www/nginx picked up 1.30.7 in 91ec63eb62c6 (“Pullup ticket #7388 … www/nginx: Security fix”) on 2026-11-19.
  • NixOS channels (local nixpkgs clone at each channel’s revision, scripts/nixpkgs-versions; releases via scripts/nixos-first-shipped):
    • Versions read from pkgs/servers/http/nginx/stable.nix and mainline.nix; no file names a tracked CVE.
    • nixos-unstable first shipped the fix in release nixos-26.11pre1124497.0bb8272318b4, found against 203fe5844740.
    • nixos-unstable-small first shipped the fix in release nixos-26.11pre1123956.d00708e733dc, found against 203fe5844740.
    • nixos-26.05-small first shipped the fix in release nixos-26.05.14730.1e6cf0d7cf5f, found against 1e6cf0d7cf5f.
    • nixos-26.05 first shipped the fix in release nixos-26.05.14753.3457b69ac4ab, found against 1e6cf0d7cf5f.
    • nixpkgs-unstable first shipped the fix in release nixpkgs-26.11pre1124565.19cfded70b91, found against 203fe5844740.
  • nixpkgs branches (local clone, first-parent history):
    • master: f0a5d452ddf1 (nginx 1.30.6 → 1.30.7) and 5cca2244da82 (nginxMainline 1.31.8 → 1.31.9), merged together as 203fe5844740 (#589961) on 2026-11-18.
    • release-26.05: backported as 1e6cf0d7cf5f (#589970) on 2026-11-18.

References

SourceURL
nginx security advisorieshttps://nginx.org/en/security_advisories.html
nginx CHANGES (mainline)https://nginx.org/en/CHANGES
nginx CHANGES-1.30 (stable)https://nginx.org/en/CHANGES-1.30
F5 K000164058 (index of the 2026-11-18 notification)https://my.f5.com/manage/s/article/K000164058
F5 K000163926 (CVE-2026-123007)https://my.f5.com/manage/s/article/K000163926
F5 K000163928 (CVE-2026-123633)https://my.f5.com/manage/s/article/K000163928
F5 K000163927 (CVE-2026-121810)https://my.f5.com/manage/s/article/K000163927
F5 K000163925 (CVE-2026-123634)https://my.f5.com/manage/s/article/K000163925
F5 K000163931 (CVE-2026-113425)https://my.f5.com/manage/s/article/K000163931
F5 K000163930 (CVE-2026-118899)https://my.f5.com/manage/s/article/K000163930
F5 K000163933 (CVE-2026-125283)https://my.f5.com/manage/s/article/K000163933
F5 K000163935 (CVE-2026-123640)https://my.f5.com/manage/s/article/K000163935
F5 K000163934 (CVE-2026-120967)https://my.f5.com/manage/s/article/K000163934
F5 K000163932 (CVE-2026-120993)https://my.f5.com/manage/s/article/K000163932
NGINX2Roothttps://nginx2root.com
Xint: NGINX2Root write-uphttps://xint.io/blog/nginx2root-remote-code-execution
Wiz Research: CVE-2026-123633 and CVE-2026-123007https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
CVE-2026-123007https://www.cve.org/CVERecord?id=CVE-2026-123007
Debian security trackerhttps://security-tracker.debian.org/tracker/CVE-2026-123007
NixOS security trackerhttps://tracker.security.nixos.org/