# NGINX HTTP/2 CVE-2026-123007 and the 18 Nov 2026 nginx security release: detection pack

Pack 1.0.0, 18 Nov 2026. Store folder `nginx-http2-cve-2026-123007-2026-11/`, published to hubfs
`nginx-cve-2026-123007-pack-v1` (the page links that hubfs folder; the store folder name stays as it is).

## At a glance

| | | Source |
|---|---|---|
| Main CVE | CVE-2026-123007, memory corruption in HTTP/2 flow control (ngx_http_v2_module), CWE-191 and CWE-787 | nginx.org, F5 K000163926, CVE record |
| Severity | F5 (CNA) CVSS 4.0 9.2 Critical, CVSS 3.1 8.1 High (AV:N/AC:H/PR:N/UI:N). nginx.org rates it "major" | F5, NVD |
| Also scored 9.2 Critical by F5 | CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425 | F5, NVD |
| Impact | worker crash; F5: code execution is possible "on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR". Code would run as the worker user | F5 |
| Open Source fix | 1.31.9 (mainline) and 1.30.7 (stable), both 18 Nov 2026 | nginx CHANGES, CHANGES-1.30 |
| Plus fix | 37.3.0.1 and 37.0.8.1. No fix for R33 to R36 | F5, CVE record |
| Exploitation | Not in CISA KEV (catalogue 2026.11.18, checked 20:37 GMT on 18 Nov 2026). No exploitation reported by CISA or CERT-EU as of 18 Nov 2026 | CISA KEV, CERT-EU 2026-022 |
| Distributions | Ubuntu (CVE-2026-123007, -123633): "needed" on xenial and later, trusty not affected; other CVEs vary by release. Debian: bookworm, trixie and forky/sid "vulnerable" for -123007 and -123633; no Debian entry yet for the other eight (not a sign of a fix) | Ubuntu and Debian trackers |
| Containers | Official Docker images `nginx:1.31.9` and `nginx:1.30.7` (also `mainline`, `stable`, `latest`) updated 18 Nov 2026, 17:18 to 17:20 GMT | Docker Hub |

**Patch now regardless of KEV status.** Then do a full restart or a binary upgrade: a reload keeps the old binary.

## Affected and fixed, every CVE in the release

Open Source ranges are from the nginx.org security advisories page. Plus ranges are from the F5 articles; R33 is added
from the CVE records, which list "R33" and later as affected (F5's tables list R34 to R36). F5 evaluates only
releases still in technical support.

| CVE | Component | nginx.org | F5 CVSS 4.0 / 3.1 | Open Source affected | Open Source fixed | Plus affected (F5) | Plus fixed (F5) |
|---|---|---|---|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control | major | 9.2 Critical / 8.1 High | 1.9.5 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0.1, 37.0.0 to 37.0.7.1, R33 to R36 | 37.3.0.1, 37.0.8.1; none for R33 to R36 |
| CVE-2026-123633 | HTTP/2 use-after-free when worker_connections run short | medium | 9.2 Critical / 8.1 High | 1.19.7 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.1.1, 37.0.0 to 37.0.6.1, R33 to R36 | 37.2.0.1, 37.0.7.1 |
| CVE-2026-123634 | resolver use-after-free with subrequests | medium | 9.2 Critical / 8.1 High | 0.6.18 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0.1, 37.0.0 to 37.0.7.1, R33 to R36 | 37.3.0.1, 37.0.8.1 |
| CVE-2026-121810 | HTTP/3 use-after-free | medium | 9.2 Critical / 8.1 High | 1.25.0 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0.1, 37.0.0 to 37.0.7.1, R33 to R36 | 37.3.0.1, 37.0.8.1 |
| CVE-2026-113425 | mail proxy use-after-free | major | 9.2 Critical / 8.1 High | 0.5.33 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0, 37.0.0 to 37.0.7, R33 to R36 | 37.3.0, 37.0.8 (CVE record: 37.3.0.1, 37.0.8.1) |
| CVE-2026-118899 | endless loop reading a request body over TLS 1.3 | major | 8.7 High / 7.5 High | 1.13.0 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0, 37.0.0 to 37.0.7, R33 to R36 | 37.3.0.1, 37.0.8.1 |
| CVE-2026-125283 | try_files with alias (and map regex captures) overflow | minor | 6.9 Medium / 5.3 Medium | 0.9.6 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0, 37.0.0 to 37.0.7, R33 to R36 | 37.3.0, 37.0.8 (CVE record: 37.3.0.1, 37.0.8.1) |
| CVE-2026-120993 | PROXY protocol v2 with dynamic certificates, NULL dereference | minor | 6.9 Medium / 5.3 Medium | 1.31.4 to 1.31.8 (F5 and the CVE record add 1.30.6) | 1.31.9 (F5 also lists 1.30.7) | 37.2.0, R33 to R36 | 37.3.0 (CVE record: 37.3.0.1) |
| CVE-2026-123640 | stream ssl_preread ClientHello parsing | minor | 6.9 Medium / 5.3 Medium | 1.15.2 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0, 37.0.0 to 37.0.6, R33 to R36 | 37.2.0.1, 37.0.7.1 |
| CVE-2026-120967 | stream SNI client certificate check | medium | 6.3 Medium / 4.8 Medium | 1.25.5 to 1.31.8 | 1.31.9, 1.30.7 | 37.1.0 to 37.2.0, 37.0.0 to 37.0.7, R33 to R36 | 37.3.0, 37.0.8 (CVE record: 37.3.0.1, 37.0.8.1) |

This pack uses the word only for the five CVEs F5 scores 9.2 Critical. The CISA ADP (Vulnrichment) entry on every record says
"Exploitation: none".

## Corrections to the original flag

1. **Severity.** The flag called CVE-2026-123007 the only critical one. F5 scores five CVEs in this release at
   CVSS 4.0 9.2 Critical: CVE-2026-123007, -123633, -123634, -121810 and -113425. nginx.org rates them "major" or "medium".
2. **Three more CVEs.** The same release also fixes CVE-2026-118899 (8.7 High), CVE-2026-123640 (6.9 Medium) and
   CVE-2026-120993 (6.9 Medium). CVE-2026-120993 is in the 1.31.9 CHANGES only, not in CHANGES-1.30. nginx.org lists
   it as 1.31.4 to 1.31.8, while F5 and the CVE record list 1.30.6 as affected and 1.30.7 as the fix. The checker treats
   1.30.6 as AFFECTED and 1.30.7 or later on the 1.30 branch as REVIEW for this CVE only.
3. **CVE-2026-123633 Plus range.** It is 37.1.0 to 37.1.1 and 37.0.0 to 37.0.6.1, fixed in 37.2.0.1 and 37.0.7.1. The flag's
   Plus ranges (37.1.0 to 37.2.0.1, 37.0.0 to 37.0.7.1) are those of CVE-2026-123007.
4. **R33.** F5's tables list R34 to R36 with no fix; the CVE records list R33 and later as affected. This pack
   includes R33 to R36. Releases before R33 are not evaluated by F5; the checker reports them as REVIEW.
5. **Mitigation source.** F5 lists "Mitigation: None" for CVE-2026-123007, -123633, -121810 and -118899. The HTTP/2
   workaround comes from CERT-EU (credited below), not F5.
6. **Exploitation wording.** Not in CISA KEV (2026.11.18). CERT-EU: "no exploitation in the wild has been reported yet".
   This pack reports only what CISA and CERT-EU have said.
7. **Left out.** The nickname, public exploit code, the kernel chain to root, the cloud-provider claim and the module
   blocking step appear only in security-firm write-ups, not in nginx.org, F5, NVD, cve.org, Ubuntu, Debian, CISA or
   CERT-EU. They are not repeated here and there is no hunt for them.
8. **Source differences kept as found.** For CVE-2026-113425, -125283 and -120967, F5 tables give 37.3.0 and 37.0.8 as
   fixes and the CVE records give 37.3.0.1 and 37.0.8.1; the checker uses the later builds (conservative). The F5 table
   for CVE-2026-118899 shows an incomplete Open Source row; the nginx.org range is used. The nginx.org page prints
   "CVE-CVE-2026-121810" and the CVE record gives the lower bound as "1.25.09"; this pack uses 1.25.0.

Checked and held: Open Source 1.9.5 to 1.31.8 for CVE-2026-123007, the 1.31.9 and 1.30.7 fixes on 18 Nov, Plus 37.3.0.1
and 37.0.8.1, the official Docker image updates, and unfixed Ubuntu and Debian packages on 18 Nov.

## Response

**Vendor fix (credited to nginx.org and F5):** upgrade Open Source to 1.31.9 or 1.30.7 and Plus to 37.3.0.1 or
37.0.8.1. R33 to R36 have no fix: move to 37.x.

**Vendor mitigations (credited to F5), per CVE until patched:**

- CVE-2026-123634: avoid SSI or mirror directives, and avoid a proxied server name built with variables.
- CVE-2026-113425: restrict listeners to trusted networks.
- CVE-2026-125283: use named regex captures; do not reuse capture variables.
- CVE-2026-120967: set `ssl_verify_client on;` in the default server of the shared listener, or move the server to its own address and port.
- CVE-2026-120993: `proxy_protocol off;` or PROXY v1, or both `ssl_session_tickets off;` and `ssl_session_cache off;`. F5: builds with BoringSSL or AWS-LC are not affected.
- CVE-2026-123640: stop using `ssl_preread` and terminate TLS on nginx.
- CVE-2026-123007, -123633, -121810, -118899: F5 lists none.

**HTTP/2 workaround (credited to CERT-EU):** "disabling HTTP/2 on exposed listeners (by removing the http2 from the
listen directives, or set http2 off;) mitigates the vulnerabilities CVE-2026-123007 and CVE-2026-123633". It does not
cover the other CVEs.

**Restart after patching (nginx documentation):** a reload (HUP) re-reads the configuration and starts new workers
from the running master, so the old binary stays in memory. Restart nginx, or upgrade the executable on the fly
(USR2, then QUIT the old master). The checker's `--proc` option and KQL Q8 look for masters that still run a deleted
or replaced binary.

**Manual step, network (OUR STEP, not in the checker): confirm HTTP/2 from outside.** Run this from a machine you are
allowed to test from, against your own hosts only, and against origins directly when they sit behind a CDN:

    openssl s_client -connect host.example:443 -alpn h2 </dev/null 2>/dev/null | grep -i 'ALPN protocol'

"ALPN protocol: h2" means HTTP/2 is offered on that listener. No ALPN line, or "No ALPN negotiated", means it is not.

**OUR ADVICE (CybaVerse, not from nginx.org, F5 or CERT-EU): rotation and rebuild checklist**

1. Inventory every nginx: servers, reverse proxies, ingress controllers, appliances and images that embed it. Run
   the checker with `--version-file` and `--conf` (and `--prefix` for images), and KQL Q6 for Defender inventory.
2. Patch internet-facing listeners first. Where you cannot patch today, apply the HTTP/2 workaround and the F5
   mitigations above, and turn off HTTP/3 (`quic` listeners) where it is not needed.
3. After patching, restart nginx and rerun the checker with `--proc` to confirm no master runs the old binary.
4. Hunt (Q1 to Q8 and the Sigma rules) back to at least 30 days before patching. Treat a shell under a worker as an
   incident.
5. If compromise is suspected: isolate the host, keep memory and core dumps (they can hold secrets), rotate the TLS
   private keys, upstream credentials, API keys and tokens the host could read, then rebuild from a patched image
   rather than cleaning in place.
6. For distribution packages, follow the Ubuntu and Debian trackers; packages were still unfixed on 18 Nov 2026.

## Hunts (all OUR PATTERN)

`kql/nginx-http2-cve-2026-123007-hunting.kql`, for Microsoft Sentinel and Defender advanced hunting. There are no
published IOCs for these CVEs; this pack invents none. Each hunt is a lead to review, not proof.

| Hunt | Table | What it finds | MITRE ATT&CK |
|---|---|---|---|
| Q1 | DeviceProcessEvents | Shells, interpreters, downloaders or other children under an nginx worker | T1190 Exploit Public-Facing Application; T1059.004 Command and Scripting Interpreter: Unix Shell |
| Q2 | Syslog | "worker process ... exited on signal" bursts and kernel segfault lines for nginx (CERT-EU names the first) | T1499.004 Endpoint Denial of Service: Application or System Exploitation |
| Q3 | Syslog | systemd-coredump "dumped core" for nginx | T1499.004 Endpoint Denial of Service: Application or System Exploitation |
| Q4 | DeviceNetworkEvents | Outbound IP and port pairs from nginx not seen in a 14-day baseline | T1190 Exploit Public-Facing Application |
| Q5 | DeviceEvents, DeviceNetworkEvents | DNS lookups by nginx not seen in the baseline | T1071.004 Application Layer Protocol: DNS |
| Q6 | DeviceTvmSoftwareInventory | Installed nginx versions in an affected range (upstream version only) | |
| Q7 | Syslog (auditd) | execve of a shell or downloader by the www-data or nginx account (UNVERIFIED field layout) | T1059.004 Command and Scripting Interpreter: Unix Shell |
| Q8 | DeviceProcessEvents, DeviceFileEvents | nginx masters started before the nginx binary was last replaced | |

Q1 to Q8 parse with Kusto.Language against the Microsoft Learn schemas (0 errors). The KQL in this pack has NOT been
run against a live tenant. A clean access log does not rule exploitation out, and CERT-EU notes that a worker crash
points to an attempt, not proof of code execution.

## Sigma (all OUR PATTERN)

| Rule | Log source | Level |
|---|---|---|
| proc_creation_lnx_nginx_worker_child | Linux process_creation | high |
| proc_creation_lnx_nginx_unexpected_child | Linux process_creation | medium |
| proc_creation_win_nginx_shell | Windows process_creation | high |
| lnx_nginx_worker_crash | Linux syslog keywords | medium |
| lnx_nginx_core_dump | Linux syslog keywords | medium |
| net_connection_lnx_nginx_external | Linux network_connection | low |
| net_connection_lnx_nginx_dns | Linux network_connection | low |
| dns_query_win_nginx | Windows dns_query | low |
| lnx_auditd_web_worker_shell | Linux auditd (UNVERIFIED field layout) | medium |

`sigma check` passes with 0 errors and 0 issues. `sigma/converted/` holds Kusto output for five pipelines (none,
microsoft_xdr, microsoft_365_defender, sentinel_asim, azure_monitor). 18 conversions fail by design and are recorded
as "CONVERSION FAILED": the syslog, auditd and dns_query rules have no table in the Defender and ASIM pipelines, and
azure_monitor also has no Linux process table. KQL Q2, Q3, Q5 and Q7 cover those sources.

## Checker

`scripts/check-nginx.sh` (bash, primary) and `scripts/Check-Nginx.ps1` (PowerShell 7, for Windows nginx builds or pwsh
on Linux) take the same options, give the same output and use the same exit codes. Both are read only and offline:
they never run nginx, never use the network, never write a file and never print file contents or secrets. They print
directive names and file:line only; no TLS key is read.

    bash scripts/check-nginx.sh --version-file nginx-V.txt --conf /etc/nginx/nginx.conf
    bash scripts/check-nginx.sh --nginx-version 1.30.6 --conf /etc/nginx/nginx.conf --prefix /mnt/image
    bash scripts/check-nginx.sh --plus-version 37.2.0.1
    sudo bash scripts/check-nginx.sh --nginx-version 1.31.9 --proc
    pwsh -File scripts/Check-Nginx.ps1 -VersionFile nginx-V.txt -Conf C:/nginx/conf/nginx.conf

Save `nginx -V 2>&1` to a file yourself first; the checker never runs it. It reports:

- **Version.** Every CVE as AFFECTED, FIXED or REVIEW with the branch logic for Open Source mainline (1.31) and stable (1.30), and for Plus (37.x or Rnn).
- **Config.** Directives across `include`s (globs, depth 16, at most 256 files of up to 4194304 bytes each):
  - `listen ... http2` and `http2 on` (HTTP/2)
  - `quic` listeners and `http3 on` (HTTP/3)
  - mail and stream blocks
  - `resolver`, SSI and `mirror`
  - `try_files` with `alias`
  - stream `ssl_verify_client`, `ssl_preread` and `proxy_protocol`
- **Running master.** With `--proc`, or `--proc-root` for a saved copy, it reads `/proc/<pid>/exe` and the process start time to find a master that still runs a deleted or replaced binary.

| Exit | Meaning |
|---|---|
| 0 | NOT AFFECTED: fixed for every CVE in the release and no replaced binary running |
| 1 | not used (reserved for unexpected runtime errors) |
| 2 | VULNERABLE: version in an affected range for at least one CVE |
| 3 | REVIEW: version unknown, sources disagree, unreadable file, missing include or parse warning |
| 4 | RESTART NEEDED: fixed version, but a master still runs a deleted or replaced binary |
| 5 | USAGE OR READ ERROR |

Distribution builds (for example "nginx/1.24.0 (Ubuntu)") are judged by the upstream version and flagged: they can
carry backported fixes later, so check the package against the tracker. Configuration features never lower the
verdict: an affected version is VULNERABLE even when HTTP/2 is off.

## Caveats

- The KQL in this pack has NOT been run against a live tenant. Sigma rules were checked and converted, not run.
- Not in CISA KEV: KEV due dates (BOD 26-04) apply to US federal agencies only. No exploitation reported by CISA or CERT-EU as of 18 Nov 2026.
  Patch now regardless of KEV status.
- There are no published IOCs; this pack invents none. Hunts are behaviour leads.
- The checker was tested on Linux (bash and pwsh); native Windows paths are not tested.
- The config scan is static. It does not evaluate `if`, variables or modules loaded at run time, and a missing include it reports as REVIEW may be harmless.
- The stale-binary check assumes Linux CLK_TCK of 100 for process start times and needs root to read other users' `/proc/<pid>/exe` links.
- F5 Distributed Cloud and NGINX One Console are marked "**" by F5: still being researched.

## Credits

Research is credited to security researchers only. nginx.org, F5, NVD, cve.org, Ubuntu, Debian, CISA, CERT-EU and
Docker Hub are cited as sources.

## Sources

- nginx CHANGES: https://nginx.org/en/CHANGES and https://nginx.org/en/CHANGES-1.30
- nginx security advisories: https://nginx.org/en/security_advisories.html
- nginx docs: https://nginx.org/en/docs/control.html, https://nginx.org/en/docs/http/ngx_http_v2_module.html, https://nginx.org/en/docs/http/ngx_http_v3_module.html
- F5: https://my.f5.com/manage/s/article/K000163926 (CVE-2026-123007), K000163928, K000163925, K000163927, K000163931, K000163930, K000163933, K000163932, K000163935, K000163934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123007 (and the other CVE IDs)
- cve.org: https://www.cve.org/CVERecord?id=CVE-2026-123007 (and the other CVE IDs)
- Ubuntu: https://ubuntu.com/security/CVE-2026-123007
- Debian: https://security-tracker.debian.org/tracker/CVE-2026-123007
- CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- CERT-EU: https://cert.europa.eu/publications/security-advisories/2026-022/
- Docker Hub official image: https://hub.docker.com/_/nginx
- MITRE ATT&CK: https://attack.mitre.org/

## Files

- `README.md` this file
- `scripts/check-nginx.sh`, `scripts/Check-Nginx.ps1` read-only checkers
- `kql/nginx-http2-cve-2026-123007-hunting.kql` hunts Q1 to Q8
- `sigma/*.yml` 9 rules; `sigma/converted/` Kusto conversions
- `tests/` shared cases, bash tests, Pester tests, fixtures (all marked FIXTURE_ONLY), KQL parse, Sigma conversion,
  static gates, negative gates and `run_all.sh`
