Introduction
A single crafted TLS 1.3 connection is enough to pin an NGINX worker process in an endless loop, leaving it unable to accept new connections or finish the ones it already holds. NGINX commonly sits in front of web applications, APIs, and Kubernetes ingress, so the fix reaches well beyond NGINX Open Source into a long list of F5 products built on the same request body code.
F5 disclosed CVE-2026-118899 on 18 November 2026. The CVE record assigns a CVSS 3.1 score of 7.5 and a CVSS 4.0 score of 8.7, and classifies the weakness as CWE 835 (loop with an unreachable exit condition). The attacker needs no authentication and no user interaction. F5 describes the impact as a data-plane denial of service with no control-plane exposure, and lists no mitigation other than upgrading.
As for exploitation status, F5 says the issue was discovered internally. Neither the F5 advisory nor the CVE record identifies a threat actor, reports attacks in the wild, or references a public exploit. The absence of such reports in these records does not prove that exploitation has not occurred.
Technical information
Trigger conditions
According to the advisory, the vulnerable configuration requires:
- A
listendirective with thesslparameter in thehttpblock - TLSv1.3 enabled
- A specially crafted TLS connection that reaches the point where the worker reads the HTTP request body
The CVSS 3.1 vector reflects a network-reachable, low-complexity attack with availability as the only impacted property:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD has not yet provided its own assessment and displays the F5-supplied score.
Root cause
The bug lives in ngx_http_do_read_client_request_body() in src/http/ngx_http_request_body.c. The fixing commit describes the read pattern in that function as:
do { c->recv() } while (c->read->ready)
The function keeps calling recv for as long as the read event is still flagged as ready. On a plain socket that is fine, because once the kernel has nothing left to return, the ready flag clears and the loop exits.
Over SSL the assumption breaks. c->recv() can return NGX_AGAIN (nothing to do right now) after OpenSSL reports SSL_ERROR_WANT_WRITE, and in that case c->read->ready can stay set. The commit points to the older changeset 7351:2b5528023f6b for this behaviour. Since the loop exit decision looked only at c->read->ready and rb->rest == 0, the function never reaches the branch that arms client_body_timeout and hands control back to the event loop. The worker spins indefinitely on that one connection, and every other connection assigned to that worker stops being served.
Why TLS 1.3
The sources do not explain why TLS 1.3 specifically is required, so treat the following as our inference. In TLS 1.3 the server sometimes has to write in the middle of a read, for example to answer a client KeyUpdate message. If the send path is blocked at that moment, OpenSSL returns SSL_ERROR_WANT_WRITE from the read call. A client controls both when it sends such messages and how quickly it drains data from the server, so it can deliberately create that state.
Attack flow
Based on the advisory and the commit description:
- The attacker targets an NGINX server whose
httpblock has alisten ... sslsocket with TLS 1.3 enabled. - The attacker opens a TLS 1.3 connection and sends an HTTP request with a body, so the worker enters
ngx_http_do_read_client_request_body(). - The attacker shapes the connection so the SSL layer needs to write during a read and cannot (our inference above), causing
c->recv()to returnNGX_AGAINwhilec->read->readyremains set. - The read loop never exits and never arms the body timer, so the worker spins on that connection.
- The affected worker stops accepting new connections and stops processing existing ones.
Patch information
Fixed releases
nginx.org fixed CVE-2026-118899 on 18 November 2026 in nginx 1.31.9 (mainline) and nginx 1.30.7 (stable). The nginx.org advisory lists versions 1.13.0 through 1.31.8 as vulnerable, calls the bug an "Infinite loop while reading client request body over TLS 1.3", and rates it major. The 1.31.9 CHANGES entry says worker processes "might get caught in an endless loop while reading the request body over SSL" and credits Maxim Dounin. The GitHub release notes for 1.31.9 and 1.30.7 also list this CVE among the fixes.
F5 advisory K000163930 (internal ID NPS 260, CWE 835) lists these fixed builds for downstream products:
- NGINX Plus: 37.3.0.1, 37.0.8.1
- NGINX Instance Manager: 2.25.0
- F5 WAF for NGINX: 5.16.2, 5.14.4
- F5 DoS for NGINX: 4.13.0
- NGINX Gateway Fabric: 2.9.0
- NGINX Ingress Controller:
2026-lts-r11, 5.8.0
Some branches have no update listed yet: NGINX App Protect WAF 4.x and 5.x, NGINX App Protect DoS 4.x, NGINX Gateway Fabric 1.x, and NGINX Ingress Controller 3.x and 4.x. F5 says to move those to a branch that has the fix.
The code fix
None of the sources ties this CVE ID to a specific commit, and the commit message does not mention the CVE. The best match in the nginx/nginx repository is commit 2b129b9, "Request body: explicit handling of NGX_AGAIN." Maxim Dounin authored it (author date March 2024), it was committed on 11 November 2026 (one week before the release), and it changes only src/http/ngx_http_request_body.c. Its description, file, timing, and author all line up with the advisory and the CHANGES entry.
The diff is two additions and one deletion:
@@ -307,6 +307,7 @@ ngx_http_do_read_client_request_body(ngx_http_request_t *r) c = r->connection; rb = r->request_body; flush = 1; + n = NGX_AGAIN; ngx_log_debug0(NGX_LOG_DEBUG_HTTP, c->log, 0, "http read client request body"); @@ -432,7 +433,7 @@ ngx_http_do_read_client_request_body(ngx_http_request_t *r) break; } - if (!c->read->ready || rb->rest == 0) { + if (n == NGX_AGAIN || !c->read->ready || rb->rest == 0) { clcf = ngx_http_get_module_loc_conf(r, ngx_http_core_module); ngx_add_timer(c->read, clcf->client_body_timeout);
What the two changes do:
- The exit check now considers what
recvreturned. Previously, the decision to stop reading and wait relied only onc->read->ready(plusrb->rest == 0). Now it also stops when the lastrecvreturnedNGX_AGAIN. A would-block answer from the SSL layer always ends the read pass regardless of the ready flag, so the worker armsclient_body_timeoutand waits for the next event instead of looping. nstarts asNGX_AGAIN. Initializing the variable at the top of the function ensures the new check never reads an uninitialised value on paths whererecvwas not called during the pass.
The change is small and confined to HTTP request body reading. Configuration and the plain-socket path behave as before.
What to upgrade to
Upgrade to nginx 1.30.7 or 1.31.9 (or later), or to one of the F5 builds listed above. If you build nginx yourself or maintain a distribution backport, commit 2b129b9 is the change to check for. F5 lists no configuration workaround (for example, the advisory does not present disabling TLS 1.3 or removing the ssl parameter as a mitigation), so we do not suggest one here.
Affected systems and versions
The vulnerable configuration is an http block listen directive using the ssl parameter with TLSv1.3 enabled.
Version data is not fully aligned across sources, so check your exact build against the source relevant to your product:
- NGINX Open Source (nginx.org security page): 1.13.0 through 1.31.8 affected; fixed in 1.31.9 and later, and 1.30.7 and later.
- NGINX Open Source (F5 advisory table): lists 1.13.0 only, with no fixed version in that row.
- NGINX Plus (F5 advisory table): 37.1.0.1 through 37.2.0.1, and 37.0.0 through 37.0.7.1 affected; fixed in 37.3.0.1 and 37.0.8.1.
- NGINX Plus (F5 advisory table): Rx R34 through R36 listed, with no fixed version shown for this row.
- NGINX Plus (CVE record): 37.2.0.1 before 37.2.1.1, 37.0.0 before 37.0.8.1, and R33.
- Other F5 NGINX products: see the fixed build list and the branches without updates in the Patch information section.
F5 marks BIG IP, BIG IQ, BIG IP CNF, BIG IP Next for Kubernetes, F5OS, and F5 Insight products as not vulnerable. The advisory had not yet confirmed applicability for F5 Distributed Cloud services and NGINX One Console. F5 did not evaluate software versions that have reached End of Technical Support, so do not assume a legacy build is safe.
References
- NVD: CVE-2026-118899
- CVE Record: CVE-2026-118899
- F5 Advisory K000163930: NGINX TLSv1.3 vulnerability
- nginx security advisories
- nginx CHANGES
- nginx GitHub releases (API)
- nginx commits touching ngx_http_request_body.c (API)
- Commit 2b129b9 (API)
- Commit 2b129b9 on GitHub
- Ubuntu: CVE-2026-118899
- F5 Completes Acquisition of NGINX
- F5 NGINX product overview
- CISA Known Exploited Vulnerabilities Catalog



