Skip to main content
株式会社オブライト
株式会社オブライト

nginx Vulnerability CVE-2026-123007 (HTTP/2)

How to Check Exposure and Update to 1.31.9 / 1.30.7

Published 2026/11/197 min read

nginx CVE-2026-123007: HTTP/2 flow-control memory corruption in 1.9.5-1.31.8. Update to 1.31.9 or 1.30.7. Check commands, fixes by distro, a stopgap, FAQ.

On November 18, 2026, nginx 1.31.9 (mainline) and 1.30.7 (stable) were released, fixing CVE-2026-123007, a memory corruption bug in HTTP/2 flow control, along with nine other vulnerabilities. The nginx project rates it "major"; versions 1.9.5 through 1.31.8 are affected, and a default configuration with HTTP/2 enabled is reachable. Check your nginx version and whether HTTP/2 is enabled, then update to 1.31.9 / 1.30.7 or your distribution's fixed package. If you cannot update yet, disabling HTTP/2 is a stopgap.

This article is based on the nginx.org advisories and CHANGES, Wiz Research's write-up, the Ubuntu, Debian, Red Hat and Alpine security pages and the Docker Hub tag list as of November 19, 2026. Anything we could not confirm is stated as such. See also the November 19 vulnerability digest, the Apache HTTP Server CVE-2026-119618 guide and the Brotli CVE-2026-111497 guide.

Key points

- What happened: an integer error in nginx's HTTP/2 flow control (send window) can corrupt memory (CVE-2026-123007). nginx describes the impact as a worker crash or other impact; Wiz Research says it demonstrated unauthenticated remote code execution in a lab on a default HTTP/2 configuration. A related HTTP/2 use-after-free (CVE-2026-123633) was fixed at the same time.
- Who is affected: nginx 1.9.5-1.31.8 with HTTP/2 enabled (123007); 1.19.7-1.31.8 for 123633. NGINX Plus is also affected.
- What to do today: check with nginx -v and nginx -T | grep http2, update to 1.31.9 / 1.30.7 or the distribution's fix, and if you cannot, set http2 off;. Rapid7 has published a PoC, but exploitation in the wild is not officially confirmed.

Affected versions at a glance

EnvironmentAffected versionsFix (as of Nov 19, 2026)
nginx mainline123007: 1.9.5-1.31.8 / 123633: 1.19.7-1.31.81.31.9 (2026-11-18)
nginx stableSame1.30.7 (2026-11-18)
NGINX PlusR33 and 37.0.0 onward (per Wiz)123007: 37.0.8.1 / 37.3.0.1; 123633: 37.0.7.1 / 37.2.0.1 (per F5's CVE record and Wiz; no fix listed for R33-R36)
Docker official image1.31.8 and earlier, 1.30.6 and earlier1.31.9 and 1.30.7 tags on Docker Hub
UbuntuAffected on supported LTS (priority High)26.04: 1.28.3-2ubuntu1.13 / 24.04: 1.24.0-2ubuntu7.20 / 22.04: 1.18.0-6ubuntu14.23, and more
Debianbookworm, trixie, forky vulnerableOnly sid (1.30.6-4) fixed at the time of checking
AlpineAffected3.24 and edge: 1.30.7-r0 / 3.23 and 3.22: 1.28.3-r8
RHEL familyNot confirmedNo affected-product or errata list on the Red Hat CVE page

What is going on

HTTP/2 manages how much data a server may send with a number called the send window, which grows when the peer sends WINDOW_UPDATE. According to Wiz, the cleanup code that refunds unsent data (ngx_http_v2_filter_cleanup()) does not check against the HTTP/2 maximum window, so a later unsigned bounds check underflows and the bad value leads to an out-of-bounds copy in the TLS send path. The bug dates back to 2015 (nginx 1.9.5).

nginx itself says only that a worker might crash or have other impact. Wiz says it built a working exploit in the lab against nginx serving static files over HTTPS on 64-bit systems, but notes it is difficult (memory disclosure, heap grooming) and needs many WINDOW_UPDATE frames. CVE-2026-123633 is a use-after-free in HTTP/2 when worker_connections run short, more likely to be exploited in reverse-proxy setups; nginx rates it medium.

CVSS and exploitation

For CVE-2026-123007, Wiz gives CVSS 4.0 of 9.2 (Critical). The Ubuntu page lists CVSS 3.x 8.1 (High) and CVSS 4.0 9.2 (Critical), priority High. Red Hat lists CVSS 3.1 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) as preliminary. The CVE.org record from F5 (the CNA) also lists CVSS 3.1 8.1 and CVSS 4.0 9.2. CVE-2026-123633 has the same F5 scores (8.1 / 9.2), although nginx.org rates it medium.

Wiz did not release its exploit, but Rapid7 published a proof-of-concept for CVE-2026-123007 on GitHub. Per Rapid7 it targets a linux/amd64 Docker image of nginx 1.31.8 with HTTP/2 and TLS, needs about 128 GB of HTTP/2 traffic, and depends on an AVX-512 glibc memcpy path. No primary source reports exploitation in the wild; CISA's assessment in the CVE record is "Exploitation: none" (Nov 18) and it is not in KEV. So: a public PoC exists, but exploitation is not officially confirmed. Update promptly. (Rapid7)

How to check

nginx -v
sudo nginx -T 2>/dev/null | grep -nE 'http2'
curl -sI --http2 https://example.com/ -o /dev/null -w '%{http_version}\n'
docker exec CONTAINER nginx -v
dpkg -l nginx | tail -n 1   # Debian / Ubuntu
rpm -q nginx                 # RHEL family

listen 443 ssl http2; (before 1.25.1) or http2 on; (1.25.1 and later) means HTTP/2 is enabled. A curl result of 2 means the server answered with HTTP/2. Distribution packages may carry backported fixes with old version numbers, so check the package changelog.

Fixing by environment

- nginx.org packages / source builds: update to 1.31.9 (mainline) or 1.30.7 (stable), run nginx -t, restart and confirm with nginx -v.
- Ubuntu: fixed in 26.04 LTS 1.28.3-2ubuntu1.13, 24.04 LTS 1.24.0-2ubuntu7.20, 22.04 LTS 1.18.0-6ubuntu14.23; 20.04 and older via Pro/ESM. 14.04 is not affected (no HTTP/2).
- Debian: bookworm, trixie and forky were still vulnerable on the tracker; only sid (1.30.6-4) was fixed. Use http2 off; until packages arrive.
- RHEL family: Red Hat lists the mitigation but no affected-product or errata list we could read; check your distribution's advisory.
- Alpine / Docker: Alpine 3.24 and edge 1.30.7-r0, 3.23 and 3.22 1.28.3-r8. For Docker, rebuild on 1.31.9 or 1.30.7 tags and redeploy; restarting a container does not update nginx.
- NGINX Plus / ingress-nginx / OpenResty: Plus fixes per Wiz are 37.0.8.1 / 37.3.0.1 (123007) and 37.0.7.1 / 37.2.0.1 (123633); confirm in F5 K000163926 and K000163928. We could not confirm fixes for ingress-nginx or OpenResty.

Mitigation before patching

The nginx advisory lists no workaround other than updating. Wiz and Red Hat describe the following stopgap: on nginx 1.25.1 or later set http2 off; in affected server blocks and remove the http2 parameter from listen directives, then reload and confirm old workers have exited. Browsers fall back to HTTP/1.1 and gRPC through nginx will not work. This does not prevent the other vulnerabilities fixed in the same release (TLS 1.3 request body infinite loop CVE-2026-118899, mail proxy CVE-2026-113425, resolver CVE-2026-123634, HTTP/3 CVE-2026-121810 and others), so updating is the real fix.

listen 443 ssl;
http2 off;

Timeline

DateEvent
2026-10-21Wiz reports CVE-2026-123633 to F5 (per Wiz)
2026-11-10F5 provides a patch for review (per Wiz)
2026-11-16Wiz reports CVE-2026-123007 to F5 (per Wiz)
2026-11-17F5 confirms CVE-2026-123007 (per Wiz)
2026-11-18nginx 1.31.9 and 1.30.7 released; coordinated disclosure; Ubuntu and Alpine fixes published; Rapid7 publishes a PoC for CVE-2026-123007
2026-11-19Debian stable fixes not yet seen; no official confirmation of exploitation found

Checklist for today

- Inventory servers, containers, load balancers and ingress using nginx
- Check nginx -v (mainline 1.31.8 or earlier, stable 1.30.6 or earlier need updating)
- Check whether HTTP/2 is enabled with nginx -T | grep http2
- Update packages where fixes exist and restart; verify the version
- Where no fix exists (e.g. Debian stable), set http2 off;, reload and confirm old workers exit
- Rebuild and redeploy Docker images on 1.31.9 or 1.30.7 tags
- Check NGINX Plus and bundled products with the vendor
- Review error.log for repeated worker crashes (signal 11)

FAQ

Do I need to update if I do not use HTTP/2?

CVE-2026-123007 and CVE-2026-123633 require HTTP/2, so they do not apply without it. But other vulnerabilities fixed in the same release (TLS 1.3 request body loop, mail proxy, HTTP/3, resolver and others) do not depend on HTTP/2, so updating is still advisable.

No fixed package is available for Debian stable yet. What should I do?

At the time of checking, only sid (1.30.6-4) was fixed. Until stable packages appear, disable HTTP/2 with http2 off; and remove http2 from listen directives, then update once fixed packages are released.

Can an old version number still be fixed?

Yes. Distributions backport fixes, for example Ubuntu 24.04 LTS 1.24.0-2ubuntu7.20 and Alpine 3.23 1.28.3-r8. Check the package version and changelog for the CVE ID.

Are attacks already happening?

No exploitation in the wild is officially confirmed (CISA's CVE-record assessment was "Exploitation: none" as of Nov 18). However, Rapid7 has published a PoC for CVE-2026-123007 on GitHub, so do not wait: update to 1.31.9 / 1.30.7 or your distribution's fixed package.

Sources

株式会社オブライト

Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.

Feel free to contact us

Contact Us