Are your NGINX servers exposed to CVE-2026-123007 over HTTP/2?
F5, as the CVE assigner, scores CVE-2026-123007 CVSS 4.0 9.2 Critical, and gives the same 9.2 Critical score to four other flaws in the same 18 November release (CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425). CVE-2026-123007 is in NGINX HTTP/2 flow control. On an affected server with HTTP/2 enabled, a remote unauthenticated client can cause a heap buffer overflow, typically followed by a worker crash, and can execute code where ASLR is off or can be bypassed. The code runs as the NGINX worker. Upgrade Open Source to 1.31.9 or 1.30.7, or Plus to 37.3.0.1 or 37.0.8.1, then fully restart. F5 lists no mitigation for CVE-2026-123007. CERT-EU says turning HTTP/2 off covers this CVE and CVE-2026-123633 until you can patch.
Critical (CVSS 4.0 9.2, F5). Five CVEs in this release carry that score. Fixes released 18 November 2026
nginx released Open Source 1.31.9 (mainline) and 1.30.7 (stable) today. Official Docker Hub images for both versions are available. Ubuntu and Debian packages were still unfixed at 20:37 GMT on 18 November 2026. CVE-2026-123007 was not in CISA's Known Exploited Vulnerabilities catalogue at that check. CERT-EU says no exploitation in the wild has been reported yet, and that security researchers have demonstrated the flaw. Absence from KEV is not a finding that it has not been exploited.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 18 November 2026, 21:22 GMT.
At a Glance
Based on F5's official CVE record, nginx.org, Ubuntu, Debian, CERT-EU and a CISA KEV check at 20:37 GMT on 18 November 2026. Last updated 18 November 2026, 21:22 GMT.
Critical (CVSS 4.0 9.2, F5)
F5 also publishes CVSS 3.1 8.1 High, and gives the same 9.2 / 8.1 scores to four other CVEs in the release. nginx.org rates CVE-2026-123007 major. Network, no authentication, high attack complexity.
Fixes out, packages lagging
1.31.9 and 1.30.7 were released on 18 November, with official Docker images. Ubuntu and Debian packages were still unfixed at 20:37 GMT.
HTTP/2 enabled
Open Source 1.9.5 to 1.31.8, Plus 37.0.0 to 37.0.7.1 and 37.1.0 to 37.2.0.1, plus Plus R-line releases with no fix listed, when HTTP/2 is on.
1.31.9, 1.30.7 or Plus, then restart
Upgrade, then fully restart. F5 lists no mitigation for CVE-2026-123007. CERT-EU says turning HTTP/2 off covers this CVE and CVE-2026-123633 only.
nginx 1.31.7 and 1.30.6 security releases are published. Both remain in the CVE-2026-123007 affected range.
nginx 1.31.8 is published. It is also affected.
F5's official CVE record for CVE-2026-123007 is published. nginx 1.31.9 and 1.30.7 are released the same day.
CVE-2026-123007 is not in CISA KEV. Ubuntu and Debian packages are still unfixed. Official Docker Hub tags 1.31.9 and 1.30.7 are available.
What the flaw does
F5 says this issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes certain traffic, the HTTP/2 flow-control window can exceed the allowed threshold, which can result in a heap buffer overflow, typically followed by a worker segmentation fault. Attackers can execute code on systems where ASLR is disabled, or where ASLR can be bypassed. An attacker could crash the worker, corrupt its memory, or potentially execute code remotely. F5 says there is no control plane exposure; this is a data-plane issue only. nginx.org describes a flow-control window overflow that might cause a worker segmentation fault, or might have potential other impact. CERT-EU says the only precondition is HTTP/2 enabled on a listening port, and that demonstrated code execution is with the privileges of the NGINX worker process.
What to Do in the Next 24 Hours
Vendor advice and our advice are labelled separately. Tick both tracks.
Upgrade to the later fixed builds, then restart
- Upgrade NGINX Open Source to 1.31.9 (mainline) or 1.30.7 (stable), both released on 18 November 2026.
- Upgrade NGINX Plus to 37.3.0.1 or 37.0.8.1. Some F5 articles list 37.3.0 and 37.0.8 for CVE-2026-113425, CVE-2026-125283 and CVE-2026-120967; the official CVE records give the later builds, and those are the ones to install.
- F5's CVE records list Plus R33 as affected with no fixed version. F5's article tables, and CERT-EU citing F5, also list R34 to R36 as affected with no fix.
- The official Docker Hub nginx images 1.31.9 and 1.30.7 are available. F5's article for CVE-2026-123007, and the official CVE record, list no mitigation: the fix is to upgrade.
Inventory, confirm HTTP/2, then restart for real
- Inventory every NGINX instance, including reverse proxies, ingress controllers, containers and appliances that ship it.
- Confirm HTTP/2 is on, and test origins directly when they sit behind a CDN.
- After an upgrade, fully restart NGINX or roll a new image. A reload can leave the old binary running.
- Until you can patch, CERT-EU says you can disable HTTP/2 on exposed listeners by removing
http2fromlistendirectives or settinghttp2 off;. That workaround covers CVE-2026-123007 and CVE-2026-123633 only, and is not a mitigation F5 lists.
Proactive: Find Exposure and Patch
Work out which NGINX listeners have HTTP/2 on, upgrade them, and do not leave an old binary running.
Inventory every NGINX instance
Search your configuration management, EDR, RMM and container inventories for NGINX Open Source, NGINX Plus, official and distro packages, and products that embed NGINX, including reverse proxies, Kubernetes ingress controllers and appliances. Record the running version, not only the package name.
Confirm whether HTTP/2 is enabled
Check each server block for listen ... http2 or http2 on;. From a client, you can also probe a TLS port with:
openssl s_client -connect host:443 -alpn h2If the output includes ALPN protocol: h2, HTTP/2 is on for that listener. When the host sits behind a CDN or another proxy, test the origin directly as well as the public front door.
Upgrade to a fixed release
Install Open Source 1.31.9 or 1.30.7, or Plus 37.3.0.1 or 37.0.8.1. Those later Plus builds are the ones given in the official CVE records. Some F5 articles list 37.3.0 and 37.0.8 for CVE-2026-113425, CVE-2026-125283 and CVE-2026-120967; install 37.3.0.1 or 37.0.8.1 anyway, because they are also the fixes for CVE-2026-123007. Official tarballs are on nginx.org, and official Docker Hub library/nginx tags 1.31.9 and 1.30.7 were published on 18 November 2026 (17:19 GMT and 17:18 GMT). If you run a product that embeds NGINX, wait for that vendor's fixed build rather than assuming the Open Source version numbers apply.
Fully restart, do not only reload
Our advice is to fully restart the service, or roll a new container image, after the binary or package is replaced. A reload can leave the old master process running, and that master keeps old workers. Then confirm the running version.
If you cannot patch immediately, turn HTTP/2 off
F5 lists no mitigation for CVE-2026-123007 or CVE-2026-123633. CERT-EU says removing http2 from listen directives, or setting http2 off;, is a workaround for those two CVEs only. It is an interim control, not a substitute for the upgrade, and it does not address the HTTP/3, resolver, mail-proxy or stream flaws in the same release. If you do not need HTTP/3, turn that off too, because CVE-2026-121810 is an HTTP/3 issue.
Plan for Ubuntu, Debian and unfixed Plus R-line
At 20:37 GMT on 18 November 2026, Ubuntu and Debian still listed their nginx packages as unfixed. Use the official tarballs or Docker images until those packages appear. CERT-EU's HTTP/2-off workaround covers CVE-2026-123007 and CVE-2026-123633 only. For Plus R33, and for R34 to R36 as listed by F5 and by CERT-EU, no fixed release is given, so apply that workaround and move to a fixed Plus branch.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Version 1.0.0 covers CVE-2026-123007 and the other flaws in the 18 November release. Everything is read-only.
check-nginx.sh
A read-only, offline bash checker. It judges the Open Source or Plus version against every CVE in the 18 November release, scans included config for HTTP/2, HTTP/3, mail, stream, resolver, SSI, mirror, and try_files with alias, and can flag a master process that is still running a replaced binary. It never runs nginx, never uses the network and never prints secrets. Save nginx -V 2>&1 to a file yourself first.
bash check-nginx.sh --version-file nginx-V.txt --conf /etc/nginx/nginx.conf
sudo bash check-nginx.sh --nginx-version 1.31.9 --procCheck-Nginx.ps1
The same checks in PowerShell 7, with the same options, output and exit codes, for Windows NGINX builds or pwsh on Linux.
pwsh -File .\Check-Nginx.ps1 -VersionFile nginx-V.txt -Conf C:\nginx\conf\nginx.confKQL hunts and Sigma rules
8 KQL queries for Microsoft Sentinel and Defender XDR, and 9 Sigma rules, covering NGINX worker crashes and core dumps, unexpected child processes, and unusual outbound connections or DNS from NGINX hosts. All of these hunts are our patterns. The checkers do not include the ALPN probe; that remains a manual openssl step in the README.
Exit codes
| Code | Meaning |
|---|---|
| 0 | NOT AFFECTED: fixed for every CVE in the release, and no replaced binary still running |
| 2 | VULNERABLE: the version is in an affected range for at least one CVE |
| 3 | REVIEW: the version is unknown, sources disagree, a file could not be read, or a parse warning was raised |
| 4 | RESTART NEEDED: the version is fixed, but a master process is still running a deleted or replaced binary |
| 5 | USAGE OR READ ERROR |
Exit code 1 is reserved and is not used. An affected version is still VULNERABLE even if HTTP/2 is off. Distribution builds are judged by the upstream version; check the package against the Ubuntu or Debian tracker for backports.
Know the limits
- Both checkers are read-only and offline. They never run nginx, never use the network, never write files and never print TLS keys or other secrets.
- The KQL has not been run against a live tenant. The Sigma rules were checked and converted, not run.
- The config scan is static. It does not evaluate
if, variables or modules loaded at run time.
Reactive: How to Hunt (Our Advice)
The hunts below are CybaVerse advice, with CERT-EU's crash-monitoring note included and labelled. The detection pack above has the checkers, 8 KQL queries and 9 Sigma rules. CybaOps can run a hunt across your estate or your clients'.
Worker crashes and core dumps
CERT-EU says you can monitor for NGINX worker crashes, for example worker process ... exited on signal in the error log, but that this is not a high-fidelity indicator of successful code execution, only of possible exploitation attempts. Look for core dumps and unexpected worker restarts from 18 November onwards, and follow them up in process-creation logs.
Workers spawning unexpected child processes
NGINX workers should not normally launch shells or unexpected child processes. Hunt process-creation logs and EDR for workers starting unusual commands, and for new persistence on those hosts.
Unusual HTTP/2 traffic
Look for long-lived HTTP/2 connections with heavy inbound traffic but few requests in the access log. A clean access log does not rule this out, because a crash or memory-corruption attempt may never become a normal logged request.
Odd outbound connections or DNS from NGINX hosts
Review outbound connections and DNS from NGINX servers that do not match their usual upstreams, package mirrors or health checks.
If you suspect compromise (our advice)
- Isolate the host from untrusted networks, but do not wipe it.
- Preserve evidence: memory, core dumps, error and access logs, the running binary, and the configuration.
- From a trusted system, rotate TLS keys, certificates and any secrets that host could reach, then rebuild from a patched image or binary.
- Start incident response if a worker spawned unexpected processes or you see unexplained outbound traffic.
NGINX HTTP/2 CVE-2026-123007 FAQ
Short answers based on F5, nginx.org, Ubuntu, Debian, CERT-EU and a CISA KEV check at 20:37 GMT on 18 November 2026. Last updated 18 November 2026, 21:22 GMT.
Am I affected?
You are in scope if you run NGINX Open Source 1.9.5 to 1.31.8, including the 14 October 2026 security releases 1.31.7 and 1.30.6 and the later 1.31.8 release, or NGINX Plus 37.0.0 to 37.0.7.1 or 37.1.0 to 37.2.0.1, and HTTP/2 is enabled on a listening port. F5's CVE record lists Plus R33 as affected with no fixed version. F5's article tables, and CERT-EU citing F5, also list R34, R35 and R36 as affected with no fix. HTTP/2 is on when a listen directive includes http2, or when http2 on is set. Official Docker Hub nginx images 1.31.9 and 1.30.7 were published on 18 November 2026. CVE-2026-123633, in the same release, has a narrower Plus range: 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. Install 37.3.0.1 or 37.0.8.1 to cover CVE-2026-123007 as well.
What is the severity?
F5, as the CVE assigner, scores CVE-2026-123007 CVSS 4.0 9.2 Critical and CVSS 3.1 8.1 High, and gives the same 9.2 / 8.1 scores to CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. The attack is over the network, needs no authentication, and has high attack complexity. F5 says a heap buffer overflow in HTTP/2 flow control can crash an NGINX worker, corrupt its memory, or potentially execute code remotely, including on systems where ASLR is disabled or can be bypassed. nginx.org rates CVE-2026-123007 as major. Code execution is in the worker process, not automatically as root. F5 says there is no control plane exposure; this is a data-plane issue only. In the same release, F5 scores CVE-2026-118899 CVSS 4.0 8.7 High, and CVE-2026-123640 and CVE-2026-120993 CVSS 4.0 6.9 Medium.
Is there a patch?
Yes. nginx released Open Source 1.31.9 (mainline) and 1.30.7 (stable) on 18 November 2026. The official CVE records give NGINX Plus 37.3.0.1 or 37.0.8.1 as the fixed releases for CVE-2026-123007. Some F5 articles list 37.3.0 and 37.0.8 for CVE-2026-113425, CVE-2026-125283 and CVE-2026-120967; install the later 37.3.0.1 or 37.0.8.1 builds, which also fix CVE-2026-123007. Official Docker Hub library/nginx tags 1.31.9 and 1.30.7 were published the same day. After you replace the package or image, fully restart NGINX. A reload can leave the old master process and its workers running.
Are Ubuntu or Debian packages fixed?
Not when we checked at 20:37 GMT on 18 November 2026. Ubuntu lists xenial through 26.10 as still needing a fix, and 14.04 trusty as not affected because it has no HTTP/2. Debian lists bookworm, trixie, and forky/sid (1.30.6-3) as vulnerable, with no fixed version. Until distribution packages appear, use the official 1.31.9 or 1.30.7 tarballs or Docker images, or turn HTTP/2 off as a CERT-EU workaround for CVE-2026-123007 and CVE-2026-123633 only.
Is turning HTTP/2 off enough?
F5 lists no mitigation for CVE-2026-123007 or CVE-2026-123633; the vendor fix is to upgrade. CERT-EU says that disabling HTTP/2 on exposed listeners, by removing http2 from listen directives or setting http2 off, is a workaround for those two CVEs only. It does not fix the other flaws in the 18 November releases, such as the HTTP/3, resolver, mail-proxy and stream issues. Treat it as an interim control until you can upgrade, and keep HTTP/3 off if you do not need it.
Is a reload enough after upgrading?
Our advice is no. After you replace the NGINX binary, package or container image, fully restart the service or roll a new image. A reload can keep the old master process running, and that master keeps the old workers. The detection pack can flag a master that is still running a replaced binary (exit code 4, RESTART NEEDED). Confirm the running binary and version after the restart.
Has this been exploited?
CERT-EU said on 18 November 2026 that no exploitation in the wild had been reported yet, and that security researchers had demonstrated use of CVE-2026-123007. The CVE was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 20:37 GMT on 18 November 2026. Absence from that catalogue is not a finding that the flaw has not been exploited. Treat internet-facing NGINX with HTTP/2 as urgent.
What else did the 18 November release fix?
The same nginx 1.31.9 and 1.30.7 releases also fix CVE-2026-123633 (HTTP/2 use-after-free when worker_connections are too low), CVE-2026-123634 (resolver with subrequests), CVE-2026-121810 (HTTP/3), CVE-2026-113425 (mail proxy), CVE-2026-125283 (try_files with alias) and CVE-2026-120967 (stream SNI certificate check). They also fix CVE-2026-118899 (an SSL request-body loop, CVSS 4.0 8.7 High from F5; nginx rates it major) and CVE-2026-123640 (stream ssl_preread validation, CVSS 4.0 6.9 Medium from F5). For CVE-2026-120993, a PROXY protocol version 2 issue, nginx.org lists mainline 1.31.4 to 1.31.8, fixed in 1.31.9 only. F5 and the official CVE record also list stable 1.30.6 as affected, fixed in 1.30.7. This page follows F5 and the CVE record for stable. Those other flaws do not all share the same affected-version range as CVE-2026-123007, and CVE-2026-123633 has a different Plus range, fixed earlier in 37.2.0.1 and 37.0.7.1.
Does this affect Kubernetes ingress controllers or appliances?
The flaw is in NGINX itself when HTTP/2 is enabled, so any product that ships an affected NGINX build can be in scope, including reverse proxies, ingress controllers and appliances. Check the vendor's own advisory and version for that product. Do not assume a CDN in front of NGINX protects the origin; test the origin directly.
We are an MSP or manage many web servers. Where do we start?
Inventory every NGINX instance you manage, including those inside containers, ingress controllers and vendor appliances. Find listeners with HTTP/2 on, and confirm the running version. Upgrade to 1.31.9, 1.30.7, or Plus 37.3.0.1 or 37.0.8.1, then fully restart. Where you cannot patch immediately, CERT-EU's HTTP/2-off workaround covers CVE-2026-123007 and CVE-2026-123633 only. Ubuntu and Debian packages were still unfixed at 20:37 GMT on 18 November 2026, so plan an upstream or image upgrade for those hosts. The detection pack on this page can check versions and configuration offline.
Need help finding NGINX across the estates you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.
Sources
- nginx: CHANGES for 1.31.9 (18 November 2026)
- nginx: CHANGES-1.30 for 1.30.7 (18 November 2026)
- nginx: security advisories, including CVE-2026-123007
- F5: K000163926 (cited by the official CVE record, Ubuntu and Debian)
- NVD: CVE-2026-123007, official F5 CVE record (published 16:18 GMT, 18 November 2026)
- Ubuntu: CVE-2026-123007 (checked 20:37 GMT, 18 November 2026)
- Debian security tracker: CVE-2026-123007 (checked 20:37 GMT, 18 November 2026)
- CISA Known Exploited Vulnerabilities catalogue (checked 20:37 GMT, 18 November 2026)
- CERT-EU: Security Advisory 2026-022, Critical vulnerabilities in Nginx (18 November 2026)
- Docker Hub: official nginx images, tags 1.31.9 and 1.30.7
Related threat guides: Apache HTTP Server CVE-2026-119618. All threat guides.