What the advisory says

NGINX lists CVE-2026-118899 as an endless loop while reading a client request body over TLS 1.3. The vendor rates it major and lists upstream versions 1.13.0 through 1.31.8 as affected. The 1.31.9 change log describes worker processes getting caught in the loop while reading the request body over SSL.

A worker stuck in request processing can reduce the capacity available for other requests. This is a service availability issue. The advisory does not mean every HTTPS request causes the condition; teams should use the vendor details and their deployed configuration to decide exposure rather than infer it from TLS being enabled alone.

Checks for your systems

Confirm which NGINX builds terminate TLS 1.3 and handle client request bodies. Include upload routes, API gateways and reverse proxies. Review worker health and logs for unexplained request-processing stalls, but do not treat the absence of an alert as proof that the vulnerable code is absent.

Update to NGINX 1.31.9 or 1.30.7, or install the supported vendor package that contains the fix. Afterward, validate TLS negotiation, uploads and normal request handling, and confirm that every active instance runs the intended build. Record the package source where an operating system supplier backports the patch.