UPDATE: If records show a break-in, start incident response now. A government security center reports exploitation of an unspecified NGINX flaw that no other source has confirmed. Apply the fix for your affected NGINX build now. Check separately for the other three flaws even if HTTP/2 is off.
Check these three things.
-
System owner: confirm whether each NGINX server, including NGINX inside other products, needs NGINX 1.31.9 or 1.30.7.
Affected versions and fixes
- CVE-2026-123007: NGINX Open Source 1.9.5 through 1.31.8 is affected (nginx.org).
- CVE-2026-123633: NGINX Open Source 1.19.7 through 1.31.8 is affected (nginx.org).
- Fixed releases for both: NGINX Open Source 1.31.9 and 1.30.7, released November 18, 2026.
- NGINX Plus, from F5's CVE records:
- CVE-2026-123007: 37.1.0 before 37.3.0.1 and 37.0.0 before 37.0.8.1 are affected. Fixed: 37.3.0.1 and 37.0.8.1.
- CVE-2026-123633: 37.1.0 before 37.2.0.1 and 37.0.0 before 37.0.7.1 are affected. Fixed: 37.2.0.1 and 37.0.7.1.
- F5's records also list NGINX Plus R33 and later releases as affected and name no fixed release in that line.
- F5 does not evaluate versions past End of Technical Support.
- NGINX is often built into other products: load balancers, Kubernetes ingress controllers, appliances and container images. Each carries its own NGINX copy and needs its own fix.
- The community Kubernetes ingress-nginx controller is retired. Its final releases came out on March 19, 2026 (v1.15.1, v1.14.5 and v1.13.9). All three build on NGINX 1.27.1, inside both affected ranges, and turn HTTP/2 on by default. The project says it will receive no further releases or security patches.
- A Linux distribution package may carry a fix under an older-looking version number. Ubuntu and Debian 13 now ship fixed packages. Debian 12 had no fix when checked on November 19, 2026.
- Record for each server:
- Installed version or package.
- Source of that record.
- Date checked.
-
Operations owner: check whether HTTP/2 is turned on, and whether NGINX passes requests to backend servers.
When the risk applies
- CVE-2026-123007 applies when HTTP/2 is turned on. No other setting is required.
- CVE-2026-123633 applies when HTTP/2 is used for client connections, NGINX passes requests to a backend server, and a worker process is running low on connection slots (worker_connections).
- The CVSS vector includes AV:N, meaning network-reachable, including internal networks. It is not proof of Internet exposure.
- A server in front of NGINX, such as a CDN or another proxy, may handle HTTP/2 itself. That does not show whether NGINX behind it uses HTTP/2.
- A server that had HTTP/2 on while running an affected version was exposed for that time, even if it is fixed now.
-
Security owner: check records for unexplained NGINX worker crashes or unexpected programs started by NGINX.
What the records can show
- F5 says the usual result is a crash of an NGINX worker process. Code execution is possible where memory-layout protection (ASLR) is off or can be bypassed.
- Records to review:
- NGINX error logs for worker exits and segmentation faults.
- System crash records.
- Security alerts.
- Unexpected processes started by the NGINX worker account.
- Unexpected outbound connections.
- Limits:
- Workers can crash for unrelated reasons.
- Clean records do not prove no attack happened.
- Missing records leave the question open.
If records show a break-in, start incident response now. Apply the fix for your affected NGINX build. Check separately for the other three flaws even if HTTP/2 is off.