Find which of the ten NGINX issues of November 18, 2026 apply to you, and protect NGINX until you install 1.30.7 or 1.31.9
Summary
On November 18, 2026, F5 published an out-of-band security notification, F5 article K000164058. It has ten articles for NGINX Open Source and NGINX Plus.
- By the CVSS v4.0 scores that F5 gives, 5 are Critical, 1 is High and 4 are Medium.
- For the 5 Critical issues, F5 says that an attacker can stop or corrupt an NGINX worker process. F5 also says that the attacker can run code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass it.
- The High issue can put a worker in an endless loop. The worker then stops serving.
- Of the Medium issues, two stop a worker, one lets a client skip the client certificate check in
stream, and one can send astreamconnection to the wrong backend. - Each issue needs a specific module or configuration. A configuration that does not have it is not affected by that issue.
NGINX released 1.30.7 (stable) and 1.31.9 (mainline) on November 18, 2026. They correct all the issues that apply to their branch.
Install NGINX Open Source 1.30.7 or 1.31.9, or the NGINX Plus release in each F5 article. This is the only complete correction. Until your change window, the check script in this page tells you which issues apply to your configuration. For six issues, F5 gives a mitigation. For the other four, the only interim step is to turn off the protocol that the issue needs. We tested the script, each F5 mitigation and each interim step on NGINX Open Source 1.30.6, 1.30.7, 1.31.8 and 1.31.9. We did not test NGINX Plus.
The same notification has twelve BIG-IP and BIG-IQ issues. This page does not include them: see F5 article K000164058.
Does this apply to you?
You have more exposure if one or more of these statements is true:
- You use NGINX Open Source 1.30.6 or older, or 1.31.0 to 1.31.8.
- You use NGINX Plus R34 to R36, 37.0.x before 37.0.8.1, or 37.1.x or 37.2.x before 37.3.0.1.
- Your configuration has the condition for one of the issues. See "Conditions".
- Clients that you do not trust can connect to the listener that the condition applies to.