What the advisory says
NGINX describes CVE-2026-123007 as memory corruption in HTTP/2 flow control. Its change log says a flow-control window overflow might cause a worker process segmentation fault or have another impact. NGINX rates the issue major. The affected upstream versions are 1.9.5 through 1.31.8.
The issue is relevant where the affected NGINX build handles HTTP/2. A reverse proxy can expose that protocol even when the application behind it does not use HTTP/2. Check listener configuration, load balancer termination and any separate ingress instances before deciding that the service is out of scope.
Checks for your systems
Identify all NGINX endpoints that negotiate HTTP/2 and capture the exact running package version. Check container images and managed products, not only host packages. Ask the supplier whether a fixed release or backport is available if the version string does not match upstream release numbers.
NGINX lists 1.31.9 and 1.30.7 as fixed. Upgrade through the supported channel and validate HTTP/2 requests, upstream responses and worker health after the change. If an update must wait, discuss temporary protocol changes with the service owner and test client impact before applying them.
