Two bugs in nginx’s HTTP/2 code allow remote code execution without logging in: CVE-2026-123633 and CVE-2026-123007 . Every nginx from 1.9.5 to 1.31.8 is affected when HTTP/2 is on. The fix is in nginx 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026. Check your distribution in the table below. If there is no fix for you yet, switch HTTP/2 off until there is.
Updates#
- 18 November 2026, 17:25 UTC. Published the package status and the HTTP/2 workaround.
Package status#
Checked on 18 November 2026, 17:25 UTC, using vendor CVE trackers and the production package repositories. A distro is only green once it ships a package with both fixes.
- ✔Fixed package available
- in progressVulnerable, vendor is preparing a fix
- no fixVulnerable, no fixed package yet
- ?Vendor has not published a status yet
| Distribution | Status |
|---|---|
| Ubuntu (tracker) | |
| Ubuntu 24.04 LTS | no fix |
| Ubuntu 22.04 LTS | no fix |
| Ubuntu 26.04 LTS | no fix |
| Ubuntu 26.10 | no fix |
| Ubuntu 20.04, 18.04, 16.04Fixes for these come through Ubuntu Pro | no fix |
| Debian (tracker) | |
Debian 13 trixieVulnerable: nginx 1.26.3-3+deb13u10 | no fix |
Debian 12 bookwormVulnerable: nginx 1.22.1-9+deb12u10 | no fix |
Debian forky, sidVulnerable: nginx 1.30.6-3 | no fix |
| Red Hat and rebuilds (tracker) | |
RHEL 9Default nginx and the nginx:1.24 and nginx:1.26 module streams | no fix |
| RHEL 10 | no fix |
RHEL 8nginx:1.24 module stream | no fix |
| AlmaLinux 8, 9, 10No advisory in the AlmaLinux errata yet | no fix |
| Amazon Linux (tracker) | |
| Amazon Linux 2023"Pending Fix" for CVE-2026-123007 | in progress |
Amazon Linux 2, nginx1 extra"Pending Fix" for CVE-2026-123007 | in progress |
| Alpine (packages) | |
Alpine 3.24nginx 1.30.7-r0 | ✔ |
Alpine edgenginx 1.30.7-r0 | ✔ |
Alpine 3.23, 3.22Vulnerable: nginx 1.28.3-r7 | no fix |
Alpine 3.21Vulnerable: nginx 1.26.3-r3 | no fix |
| Fedora (updates) | |
Fedora 45, 44, 43Vulnerable: nginx 1.30.6 | no fix |
| SUSE | |
| SLES, openSUSE Leap and TumbleweedSUSE has no CVE page for either bug yet | ? |
| nginx's own builds | |
| nginx.org packages (Debian, Ubuntu, RHEL and others)Stable 1.30.7, mainline 1.31.9 (repositories) | ✔ |
Docker official imageTags nginx:1.30.7 and nginx:1.31.9 (Docker Hub) | ✔ |
| NGINX PlusR33 and 37.x are affected. Wiz lists 37.0.7.1 / 37.2.0.1 for CVE-2026-123633 and 37.0.8.1 / 37.3.0.1 for CVE-2026-123007. Check F5's advisories (K000163928, K000163926). | ✔ |
Am I affected?#
You are affected if both are true:
- Your nginx is 1.9.5 up to 1.31.8. Check with
nginx -v. - HTTP/2 is on somewhere. Check with
nginx -T 2>/dev/null | grep -n http2.
CVE-2026-123007 needs HTTP/2 over TLS. It works on a server that only serves static files. CVE-2026-123633 needs nginx to run low on free connections, which is easiest to reach when nginx proxies to a backend. Wiz’s write-up has the details. Wiz says it built working exploits for both and is not publishing them.
A CDN in front of nginx does not protect you if your origin’s IP still answers on port 443. Check that from outside before you count on it.
How to patch#
Install the fixed package, then restart nginx. A reload is not enough: the master process keeps running the old binary.
# Debian, Ubuntu (and the nginx.org apt repository)
sudo apt update && sudo apt install --only-upgrade nginx
# RHEL, AlmaLinux, Rocky, Fedora, Amazon Linux
sudo dnf upgrade nginx
# Alpine
sudo apk upgrade nginx
sudo systemctl restart nginx
For Docker, pull nginx:1.30.7 or nginx:1.31.9 and recreate the container.
Distributions backport the fix and keep their old version number. So nginx -v on Ubuntu or RHEL will not say 1.30.7. Compare the package version (dpkg -l nginx or rpm -q nginx) with the table above instead.
Check that the running process is the new binary. If this prints (deleted), nginx still runs the old one and needs a restart:
sudo ls -l /proc/$(pgrep -o -x nginx)/exe
No fix yet? Switch HTTP/2 off#
Turning HTTP/2 off blocks both bugs. Browsers fall back to HTTP/1.1, so your site keeps working.
First find every place that turns it on:
sudo grep -rn http2 /etc/nginx/
On nginx 1.25.1 and newer, set http2 off; in every server block, or once in the http block. Also remove http2 from every listen line:
server {
listen 443 ssl; # was: listen 443 ssl http2;
http2 off;
...
}
On nginx older than 1.25.1, the only switch is the http2 flag on listen. Remove it from every listen line on that port: one server block with http2 turns it on for all servers sharing that IP and port.
Test the config, reload and check from outside:
sudo nginx -t && sudo systemctl reload nginx
curl -so /dev/null -w '%{http_version}\n' --http2 https://example.com/
# 1.1 means HTTP/2 is off. 2 means it is still on.
Switch HTTP/2 back on after you have patched.
The same nginx release fixes eight other bugs, including a use-after-free in HTTP/3 (CVE-2026-121810). Switching HTTP/2 off does not cover those. The nginx security advisories list them all. Patching is the only full fix.