NGINX Open Source versions 1.9.5 through 1.31.8 contain CVE-2026-123007, a memory-corruption flaw in HTTP/2 flow control that nginx.org rates "Major." The fix is in 1.31.9 (mainline) and 1.30.7 (stable), released on 18 November 2026. Check your version with nginx -v, confirm whether HTTP/2 is enabled, upgrade, restart, and verify.
This guide is defensive only. It does not describe how the flaw is triggered beyond what the vendor's changelog says.
Who this is for and what you will have at the end
This is for administrators who run NGINX directly on Linux, in Docker, as a reverse proxy in front of an application, or bundled in a hosting panel. By the end you will know whether your servers are in scope, which version to move to, how to install it for your platform, how to switch HTTP/2 off temporarily if you cannot patch today, and how to prove the fix is running.
If you run NGINX Plus, the NGINX Ingress Controller, NGINX Gateway Fabric or the community ingress-nginx, the fixed versions are set by F5 or the project, not by nginx.org's open-source version numbers. Those pages could not be read in this run (see "What we checked"), so check the F5 advisory K000163926 and your product's release notes.
What the nginx.org advisories say
The nginx.org security advisories page lists the following for this release. All of them are fixed in 1.31.9 and 1.30.7.
| CVE | Component | nginx.org severity | Vulnerable versions |
|---|---|---|---|
| CVE-2026-123007 | Memory corruption in HTTP/2 flow control | Major | 1.9.5 to 1.31.8 |
| CVE-2026-123633 | Use-after-free in HTTP/2 | Medium | 1.19.7 to 1.31.8 |
| CVE-2026-121810 | Use-after-free in HTTP/3 | Medium | 1.25.0 to 1.31.8 |
| CVE-2026-123634 | Use-after-free in the resolver | Medium | 0.6.18 to 1.31.8 |
| CVE-2026-118899 | Endless loop reading the request body over TLS 1.3 | Major | 1.13.0 to 1.31.8 |
| CVE-2026-113425 | Use-after-free in the mail proxy module | Major | 0.5.33 to 1.31.8 |
The 1.30.7 changelog contains nine security entries in total. Besides the six above, it lists CVE-2026-125283 (a buffer overflow with try_files and alias in certain configurations), CVE-2026-120967 (client certificates verified with the wrong server's configuration in the stream module) and CVE-2026-123640 (the stream ssl_preread module interpreting malformed ClientHello messages differently from other TLS implementations).
For CVE-2026-123007 the changelog describes it in one sentence: a flow control window overflow in HTTP/2 might allow an attacker to cause a segmentation fault in a worker process, or might have other impact. Debian's security tracker adds that the window can exceed the allowed threshold, causing a heap buffer overflow that usually crashes a worker, and that code execution is possible where ASLR is disabled or can be bypassed. Read that as "crash is the realistic outcome, code execution is not ruled out."
Two things you may see in headlines were not confirmed from the sources opened here: a CVSS score for CVE-2026-123007, and whether exploitation has been seen in the wild. Check CISA's Known Exploited Vulnerabilities catalog and the F5 advisory before you decide how urgent this is for your environment.
Step 1: Check whether you are affected
Check the version
nginx -vThe output looks like nginx version: nginx/1.28.0. Anything from 1.9.5 up to and including 1.31.8 is vulnerable. The fixed releases are 1.30.7 and anything from 1.31.9 upward. Note that 1.30.x stable below 1.30.7 is vulnerable even though 1.30 is a current branch.
Check whether HTTP/2 is compiled in
nginx -V 2>&1 | tr ' ' '\n' | grep -i http_v2If this prints --with-http_v2_module, the module is present. The nginx documentation says the module is not built by default. If nothing prints, the HTTP/2 flaws do not apply to that binary.
Check whether HTTP/2 is turned on
The nginx documentation gives http2 on | off; with a default of off, valid in the http and server contexts, available since 1.25.1. The older method is the http2 parameter on the listen directive, which the documentation marks as deprecated. Search the full effective configuration for both:
sudo nginx -T 2>/dev/null | grep -n -E 'http2'# Current style
server {
listen 443 ssl;
http2 on;
}
# Older, deprecated style
server {
listen 443 ssl http2;
}Either form means the server accepts HTTP/2. Remember that a config can include other files and that a vhost in a hosting panel may enable it separately. nginx -T prints the merged configuration, which is why it is used here.
Step 2: Choose the target version
| You run | Move to |
|---|---|
| Stable branch (1.30.x) | 1.30.7 |
| Mainline branch (1.31.x) | 1.31.9 |
| Older branch (1.28, 1.26 and earlier) | The advisory lists no fixes for them: move to 1.30.7 or later |
| Distribution package (Debian, Ubuntu, RHEL family) | The distribution's patched package, once published |
Staying on the same branch is the smallest change. nginx.org's advisories name only 1.30.7 and 1.31.9 as fixed, so an end-of-life branch needs a branch change, which deserves a test run first.
Step 3: Patch by platform
Packages from nginx.org
The nginx.org Linux packages page describes the stable repository as the default and the mainline repository as a separate one you switch to. On Debian or Ubuntu, once the repository is configured as described on that page, a normal update picks up the new version:
sudo apt update
sudo apt install --only-upgrade nginx
nginx -vOn RHEL and derivatives (Rocky, AlmaLinux, Oracle Linux):
sudo yum update nginx
nginx -vIf nginx -v still shows an old version, the repository may not have the build yet or your apt pin may point at a distribution package. Check apt policy nginx.
Distribution packages
Debian's security tracker, when opened for this run, listed nginx as vulnerable in bookworm (1.22.1-9+deb12u10 in the security suite) and trixie (1.26.3-3+deb13u10), with a fix only in sid (1.30.6-4 noted there, with the upstream fix in 1.30.7). Distributions backport fixes, so the version string can stay the same after a fix. Use your distribution's tracker for CVE-2026-123007 rather than comparing version numbers to 1.30.7. Until a fixed package is published, you have two options: install from the nginx.org repository, or apply the temporary HTTP/2 disable below.
Docker
The official nginx image on Docker Hub lists 1.31.9 as mainline and 1.30.7 as stable. Pull the tag you use and recreate the container, because a running container keeps its old image:
docker pull nginx:stable
docker compose up -d --force-recreate
docker exec <container> nginx -vPin to a version tag such as 1.30.7 in production, rather than latest, so a rebuild cannot silently change versions. Also rebuild any of your own images that start FROM nginx so they pick up the new base.
Kubernetes ingress, Plus and hosting panels
For ingress controllers, NGINX Plus, cPanel or Plesk, wait for and apply the product vendor's own update. Their version numbers differ from nginx.org's. This guide does not list them because the F5 advisory page would not load in this run.
Step 4: Temporary stopgap, turn HTTP/2 off
The nginx.org advisories list no workaround. If you cannot upgrade today and need to reduce exposure, switching HTTP/2 off removes the HTTP/2 code path used by CVE-2026-123007 and CVE-2026-123633. It is a stopgap, not a fix.
server {
listen 443 ssl;
http2 off; # or remove "http2" from the listen line on older configs
}sudo nginx -t
sudo systemctl reload nginxTrade-offs to weigh first:
- Clients fall back to HTTP/1.1. Pages load more slowly on sites with many assets. Test any client that depends on HTTP/2 before you switch it off.
- It covers only the two HTTP/2 flaws. The other seven entries in the changelog (resolver, HTTP/3, mail proxy, stream,
try_fileswithalias, TLS 1.3 body reading) are unaffected by it. - Remove the stopgap once the upgrade is done and tested.
Where you can, also block direct internet access to anything that does not need it, and put a CDN or cloud load balancer that terminates HTTP/2 in front of origin servers. That is general hardening, not a documented mitigation for this CVE.
Step 5: Restart and verify
After the new binary is installed, restart the service so workers run the new code:
sudo nginx -t
sudo systemctl restart nginxA reload tells the running master process to re-read configuration; it does not substitute for restarting after a binary update. Then verify:
nginx -v
systemctl status nginx --no-pager
ps -o pid,lstart,cmd -C nginxThe lstart column should be later than the time you installed the update. For containers, docker exec <container> nginx -v must show 1.30.7 or later in the 1.30 line, or 1.31.9 or later.
What to watch afterward
The advisory describes a worker process segmentation fault as the likely effect. Watch for lines like these in the error log:
[alert] 1234#1234: worker process 1240 exited on signal 11The line above is an illustrative example of nginx's usual wording. Repeated worker exits on signal 11 before the upgrade are worth keeping for the incident record. The flaw concerns HTTP/2 protocol-level behavior, so you should not expect it to be obvious in ordinary access logs. Treat unexplained worker restarts on an HTTP/2 server as a reason to patch and investigate, not as proof of an attack.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
nginx -v shows the old version after update | Held package, apt pin to distribution, or repository not updated | apt policy nginx, apt-mark showhold, check /etc/apt/preferences.d/99nginx |
A deprecation warning about listen ... http2 | Older config style on a newer binary | Replace with http2 on; in the server block |
An "unknown directive" error for http2 | The binary is older than 1.25.1 | Use the listen ... http2 form, or upgrade |
An error that HTTP/2 needs ngx_http_v2_module | The binary was built without --with-http_v2_module | Install a package that includes the module |
| Container still reports an old version | Running container uses the old image | Pull, then recreate the container |
The exact message wording was not verified in this run; the documentation pages state the deprecation, the 1.25.1 version and the build requirement.
Checklist
- Run
nginx -von every host and container image; list anything from 1.9.5 to 1.31.8. - Run
nginx -T | grep http2to find which servers use HTTP/2. - Upgrade to 1.30.7 or 1.31.9, or install your distribution's fixed package.
- If you cannot patch today, set
http2 off;as a stopgap and note the date to remove it. - Restart (not just reload) and confirm the version and process start time.
- Check product vendors (F5, Plesk, cPanel, ingress controllers) for their own fixed versions.
- Review CISA KEV and the F5 advisory for exploitation status.
For the related Java and Oracle patching this week, see Java4Shell: check exposure, patch and apply the workaround and Oracle November 2026 CSPU: what to patch first.
What we checked
- Opened the nginx.org security advisories page on 2026-11-19. CVE-2026-123007 is listed as "Memory corruption in HTTP/2 flow control," severity Major, vulnerable 1.9.5 to 1.31.8, not vulnerable in 1.31.9+ and 1.30.7+. CVE-2026-123633 is listed as Medium, vulnerable 1.19.7 to 1.31.8. The page shows no workaround and no publication dates.
- Opened the nginx.org 2026 news page and the CHANGES-1.30 file on 2026-11-19. Both show 1.30.7 (stable) and 1.31.9 (mainline) dated 18 Nov 2026. We counted nine "Security:" entries under "Changes with nginx 1.30.7" and quoted their CVE IDs in this article.
- Cross-checked the two against each other: the advisories page and the changelog agree on the fixed versions and on the CVE IDs for HTTP/2.
- Opened the ngx_http_v2_module documentation:
http2 on | off;, defaultoff, contextshttpandserver, since 1.25.1; the module is not built by default. The ngx_http_core_module documentation marks thehttp2parameter oflistenas deprecated. - Opened the Debian security tracker entry for CVE-2026-123007 on 2026-11-19: bookworm and trixie (including their security suites) marked vulnerable, sid 1.30.6-4 marked fixed.
- Opened the Docker Hub nginx page: 1.31.9 shown as mainline, 1.30.7 as stable.
- Documented output: none of the commands were run against a live server. The
nginx -vexample output is illustrative. - Not checked: the F5 advisory K000163926 would not load (the myF5 page showed an error), so we could not confirm the CVSS score, NGINX Plus, Ingress Controller or Gateway Fabric fixed versions, or exploitation status. A claim that a public proof of concept exists was not verified and is left out. Not tested on a live NGINX server; steps follow the vendor documentation as of 2026-11-19.
Last tested: 2026-11-19
References
- nginx security advisories: https://nginx.org/en/security_advisories.html
- nginx news 2026: https://nginx.org/2026.html
- nginx changes, 1.30 branch: https://nginx.org/en/CHANGES-1.30
- ngx_http_v2_module: https://nginx.org/en/docs/http/ngx_http_v2_module.html
- ngx_http_core_module, listen: https://nginx.org/en/docs/http/ngx_http_core_module.html#listen
- nginx Linux packages: https://nginx.org/en/linux_packages.html
- Debian security tracker, CVE-2026-123007: https://security-tracker.debian.org/tracker/CVE-2026-123007
- Official nginx image on Docker Hub: https://hub.docker.com/_/nginx
- F5 advisory K000163926: https://my.f5.com/manage/s/article/K000163926
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.