
THREAT LEVEL - HIGH
19-11-2026
High Level – New Critical NGINX Vulnerabilities Could Allow Remote Code Execution
Threat Level Description
IthacaLabs has maintained the Threat Level (High) adding a new observation:
An attack is highly likely. Addressing the broad nature of the threat in order to reach an acceptable risk level, requires additional and sustainable protective security measures combined with specific business and geographical vulnerabilities and judgments.
Description
We have observed two new critical vulnerabilities in NGINX, the widely used web server and reverse proxy, that can allow remote, unauthenticated attackers to execute code on affected servers.
The critical vulnerabilities, CVE-2026-123633 and CVE-2026-123007, are memory-safety flaws in how NGINX handles HTTP/2 traffic and affect only servers with HTTP/2 enabled. They can crash NGINX, and they allow code execution where address space layout randomization (ASLR) is disabled or can be bypassed. CVE-2026-123007 dates back to NGINX 1.9.5.
Remote code execution has been confirmed, including on NGINX servers that only serve static files. The vulnerabilities are not currently known to be exploited in the wild.
F5 has released fixed versions and Ubuntu has published updated packages, while Red Hat fixes are still pending. Because one NGINX server often fronts several websites and APIs, a single compromise can expose multiple applications. Organizations running NGINX with HTTP/2 enabled may be at elevated risk of compromise.
Our Advisory and Managed Services, including our Security Operations and Technology Resilience lines, can help safeguard your organization against such threats.
Through proactive monitoring, threat detection, and incident response, our services are designed to keep your systems secure, resilient, and prepared for evolving cyber risks. We advise all organizations to remain vigilant and regularly review their cybersecurity postures.
Affected Products:
- NGINX Open Source 1.9.5 to 1.31.8, fixed in 1.30.7 and 1.31.9
- NGINX Plus R33 to R36, and 37.x before 37.0.8.1 and 37.3.0.1
- NGINX Ingress Controller, NGINX Gateway Fabric and NGINX Instance Manager versions listed by F5
- F5 WAF for NGINX, NGINX App Protect WAF, F5 DoS for NGINX and NGINX App Protect DoS
- Red Hat RHEL 8, 9 and 10 nginx, Hardened Images and 3scale API Management 2 (no fix yet)
Recommendation(s):
It is highly recommended to apply the NGINX security updates released by F5, and your Linux distribution's updated packages, as soon as they are available. Organizations should also consider the following measures:
- Identify NGINX deployments with HTTP/2 enabled, including F5 products that embed NGINX such as ingress controllers and WAFs.
- Upgrade NGINX Open Source to 1.30.7 or 1.31.9, NGINX Plus to 37.0.8.1 or 37.3.0.1, and other F5 NGINX products to the fixed versions F5 lists.
- Where F5 lists no fix, such as NGINX Plus R34 to R36, move to a fixed version. NGINX App Protect WAF and DoS have none yet.
- Prioritize NGINX servers with HTTP/2 enabled that attackers can reach, as one often fronts several applications.
- If you cannot upgrade, temporarily disable HTTP/2 by removing http2 from listen directives and, on NGINX 1.25.1 or later, setting http2 off.
- Test compatibility first, confirm old workers exit after reloading, and re-enable HTTP/2 after upgrading.
- Investigate unexpected NGINX worker crashes or commands launched by NGINX.
- Ensure incident response teams are ready to investigate and rebuild compromised servers.
You should understand the importance of applying security updates with urgency, regardless of organizational size. Implementing an effective patch management strategy, enabling comprehensive event logging, and actively monitoring security events are critical to protecting business-critical assets. A comprehensive risk management approach should include regular penetration testing, at least annually and after significant system changes, to ensure continued compliance with security best practices and industry regulations.
Threat Level Description:
Threat Level: High – An attack is highly likely. Addressing the broad nature of the threat in order to reach an acceptable risk level, requires additional and sustainable protective security measures combined with specific business and geographical vulnerabilities and judgments.
References:
K000163928: NGINX ngx_http_v2_module vulnerability CVE-2026-123633 (F5)
K000163926: NGINX ngx_http_v2_module vulnerability CVE-2026-123007 (F5)
NGINX Security Advisories (nginx.org)
CVE-2026-123633 – NIST National Vulnerability Database
CVE-2026-123007 – NIST National Vulnerability Database
IthacaLabs Incident Response and Threat Intelligence Services



