Skip to content
nginx HTTP/2 RCE (CVE-2026-123633, CVE-2026-123007): patch status per distro

nginx HTTP/2 RCE (CVE-2026-123633, CVE-2026-123007): patch status per distro

Ma.Ttias.Be • November 18, 2026

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. The best fix is to upgrade from nginx’s upstream repo . It already has the fix. Otherwise check your distribution in the table below. Switch HTTP/2 off until it has a fix.

18 November 2026, 22:48 UTC. AlmaLinux 10 and AlmaLinux 9’s default nginx are fixed, ahead of Red Hat. See the package status .

18 November 2026, 20:27 UTC. Added SUSE’s status (still analysing) and openSUSE Tumbleweed (no fix) to the package status .

18 November 2026, 17:53 UTC. Added Arch Linux to the package status and steps to switch to nginx.org’s packages .

18 November 2026, 17:25 UTC. Published the package status and the HTTP/2 workaround.

Checked on 18 November 2026, 22:48 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 progress Vulnerable, vendor is preparing a fix

no fix Vulnerable, no fixed package yet

? Vendor is still analysing, status not confirmed

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. That 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. It 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.

Whatever you install, restart nginx afterwards. A reload is not enough. The master process keeps running the old binary.

Use the nginx upstream repo (best fix) #

nginx’s own repository already has the fix, for every distro listed in the nginx.org row of the table.

The steps below are nginx’s official install guide , shortened.

Back up your config first: sudo cp -a /etc/nginx /etc/nginx.bak .

Accept the GPG key only if its fingerprint is 573B FD6B 3D8F BC64 1079 A6AB ABF5 BD82 7BD9 BF62 .

For Amazon Linux 2023. Accept the GPG key only if its fingerprint is 573B FD6B 3D8F BC64 1079 A6AB ABF5 BD82 7BD9 BF62 .

Then check the switch worked:

nginx -v now says 1.30.7.

sudo nginx -t passes. nginx.org’s default nginx.conf includes conf.d/*.conf , not Debian’s sites-enabled/ . If apt asked nginx.conf and you took the new one, add the include line for your sites back.

Dynamic modules from the distro ( libnginx-mod-* on Debian, nginx-mod-* on RHEL) do not load into nginx.org’s build. nginx.org ships its own nginx-module-* packages for the common ones.

Or update your distro’s package #

Once your distro is green in the table, a normal update is enough:

Arch does not support partial upgrades, so this is a full system upgrade.

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 the running nginx #

Check that the running process is the new binary. If this prints (deleted) , nginx still runs the old one and needs a restart:

Or 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:

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:

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:

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.

Extracted Entities