November 19, 2026
Accorian would like to alert you to two newly disclosed critical vulnerabilities affecting NGINX Open Source and NGINX Plus, tracked as CVE-2026-123633 and CVE-2026-123007, that could allow unauthenticated attackers to execute malicious code on vulnerable servers.
Disclosed on November 18, 2026, the vulnerabilities affect HTTP/2 processing within the NGINX ngx_http_v2_module. Under specific conditions, attackers could exploit these flaws to corrupt server memory, crash NGINX worker processes, or potentially execute arbitrary code on affected systems.
Both vulnerabilities have been assigned a CVSS v4.0 score of 9.2 (Critical) and a CVSS v3.1 score of 8.1 (High). F5 has released security updates addressing the vulnerabilities and recommends that organizations upgrade affected deployments.
Although no confirmed exploitation in the wild had been reported at the time of disclosure, security researchers from Wiz, Xint, and other organizations have demonstrated successful exploitation in controlled environments. Research has also identified potential attack chains that could lead to root-level access under specific conditions.
Organizations operating NGINX-based web servers, reverse proxies, API gateways, and other internet-facing infrastructure should assess their exposure and prioritize remediation.
How the Vulnerabilities Work
The vulnerabilities exploit memory management and HTTP/2 flow-control weaknesses within the NGINX HTTP/2 module, potentially allowing remote attackers to compromise affected servers without authentication.
Attackers may exploit these vulnerabilities through the following mechanisms:
HTTP/2 Use-After-Free (CVE-2026-123633): The vulnerability occurs when NGINX proxies HTTP/2 client requests to backend servers while available worker connections are exhausted or running low. Under certain conditions, improper memory handling can result in a use-after-free condition, potentially allowing memory corruption and unauthorized code execution.
HTTP/2 Integer Underflow (CVE-2026-123007): A flaw in HTTP/2 flow-control processing can cause an integer underflow, allowing the flow-control window to exceed its permitted threshold. This may result in a heap buffer overflow, potentially enabling attackers to corrupt memory and execute malicious code.
Unauthenticated Remote Code Execution: Attackers may send specially crafted HTTP/2 requests to vulnerable NGINX servers. Under specific conditions, successful exploitation could allow arbitrary code execution with the privileges of the NGINX worker process.
Application Disruption: Exploitation attempts may crash NGINX worker processes, causing denial-of-service conditions and interruptions to websites, APIs, and business-critical applications.
Potential System Compromise: Successful remote code execution could enable attackers to access sensitive application data, manipulate server processes, or establish unauthorized access. Researchers have also demonstrated potential privilege escalation to root through additional exploit chains.
Researchers have demonstrated the feasibility of exploiting both vulnerabilities in controlled environments. While the vulnerabilities primarily affect the NGINX data plane, successful exploitation could compromise the applications and infrastructure that depend on affected servers.
Affected Systems
The vulnerabilities affect NGINX Open Source and NGINX Plus deployments that have HTTP/2 enabled.
Affected versions include:
NGINX Open Source
- CVE-2026-123633: Versions 1.19.7 through 1.30.6 (stable) and 1.31.0 through 1.31.8 (mainline).
- CVE-2026-123007: Versions 1.9.5 through 1.30.6 (stable) and 1.31.0 through 1.31.8 (mainline).
NGINX Plus
- CVE-2026-123633: Versions 37.0.0 through 37.0.6.1 and 37.1.0 through 37.2.0.
- CVE-2026-123007: Versions 37.0.0 through 37.0.7.1 and 37.1.0 through 37.2.0.1.
- NGINX Plus R34 through R36 are also affected and require migration to supported, patched releases.
Fixed Versions
- NGINX Open Source Stable: 1.30.7
- NGINX Open Source Mainline: 1.31.9
- NGINX Plus 37.0.x: 37.0.8.1
- NGINX Plus 37.1.x–37.2.x: 37.3.0.1
Organizations should note that earlier NGINX Plus security updates addressing CVE-2026-123633 do not necessarily address CVE-2026-123007. Both vulnerabilities must be remediated.
F5 has indicated that BIG-IP, BIG-IQ Centralized Management, F5 Insight, F5OS, BIG-IP CNF, BIG-IP Next for Kubernetes, and F5 AI Gateway are not vulnerable to these specific issues. F5 Distributed Cloud services and NGINX One Console remained under investigation at the time of the initial advisory.
Organizations should also review NGINX instances deployed through container images, Kubernetes environments, cloud infrastructure, and third-party applications, as these deployments may not be captured in standard software inventories.
How to Check if You Are Affected (CVE-2026-123633 / CVE-2026-123007)
Organizations can perform the following checks on systems running NGINX Open Source or NGINX Plus.
Step 1: Identify the Installed NGINX Version
Run the following command:
nginx -v 2>&1
Compare the installed version with the affected version ranges listed above.
Step 2: Check Whether the HTTP/2 Module Is Available
Run:
nginx -V 2>&1 | grep — ‘–with-http_v2_module’
If the HTTP/2 module is included, proceed to verify whether HTTP/2 is enabled in the configuration.
Step 3: Check Whether HTTP/2 Is Enabled
Run:
sudo nginx -T 2>&1 | grep -E ‘http2 on|listen.*http2’
Review the output for active HTTP/2 configuration directives.
Step 4: Check for Reverse Proxy Configuration
For CVE-2026-123633, identify whether the affected NGINX instance proxies requests to backend applications.
Run:
sudo nginx -T 2>&1 | grep -E ‘proxy_pass|grpc_pass|fastcgi_pass|uwsgi_pass’
Review the configuration to determine whether relevant HTTP/2 client connections are forwarded to backend services.
Step 5: Review Worker Connection Settings
Run:
sudo nginx -T 2>&1 | grep -A 5 ‘events {‘
Identify the configured worker_connections limit. CVE-2026-123633 involves conditions in which available worker connections become exhausted or constrained.
Potentially Exposed if:
- The installed NGINX version falls within the affected version ranges and does not contain a vendor-backported fix.
- HTTP/2 is enabled on the affected server.
- The NGINX instance accepts HTTP/2 connections from untrusted clients.
- For CVE-2026-123633, the relevant backend proxying and worker-connection conditions can occur.
Not Affected by These Specific Vulnerabilities if:
- The NGINX installation has been upgraded to a version containing fixes for both CVEs.
- HTTP/2 is completely disabled across all relevant NGINX listeners.
- The deployed NGINX version predates the introduction of the vulnerable functionality, subject to vendor confirmation.
For Linux distribution packages and customized NGINX builds, organizations should review the relevant vendor security advisories, as fixes may be backported without changing the upstream NGINX version number.
These checks help identify potential exposure but do not establish whether exploitation has occurred.
Potential Business Impact
The vulnerabilities present significant risks to organizations relying on NGINX for web applications, reverse proxy services, and API infrastructure, including:
- Unauthorized execution of malicious code on affected NGINX servers.
- Potential compromise of sensitive corporate, customer, and application data.
- Disruption of business-critical websites, APIs, and digital services through worker process crashes or denial-of-service attacks.
- Unauthorized modification of hosted applications or server configurations following successful exploitation.
- Potential compromise of connected backend applications and infrastructure.
- Operational downtime, incident response costs, regulatory exposure, and reputational damage.
Internet-facing NGINX deployments handling high volumes of HTTP/2 traffic warrant particular attention, especially where reverse proxy functionality connects external requests to sensitive internal applications.
Recommended Security Actions
Accorian strongly recommends that organizations take the following precautionary measures:
Apply Security Patches Immediately: Upgrade affected NGINX deployments to the fixed versions released on November 18, 2026. For NGINX Open Source, update to version 1.30.7 (stable) or 1.31.9 (mainline). For NGINX Plus, use version 37.0.8.1 or 37.3.0.1, as appropriate. Ensure that the selected update addresses both vulnerabilities.
Identify Vulnerable NGINX Deployments: Review NGINX installations across servers, cloud environments, containers, Kubernetes ingress controllers, reverse proxies, and API gateways. Identify systems running affected versions with HTTP/2 enabled, including instances managed by third-party providers.
Prioritize Internet-Facing Infrastructure: Focus remediation on publicly accessible web servers, application gateways, API endpoints, and reverse proxies that process untrusted HTTP/2 requests. Evaluate systems supporting business-critical applications and sensitive data flows.
Implement Temporary Mitigations: Where immediate patching is not feasible, consider disabling HTTP/2 on affected NGINX servers and using HTTP/1.1 until the appropriate updates can be applied. Review application compatibility and operational requirements before implementing configuration changes. Temporary mitigations should not replace patching.
Monitor for Suspicious Activity: Review NGINX access and error logs, unexpected worker process crashes, abnormal HTTP/2 traffic patterns, unusual child processes, and suspicious system activity that could indicate attempted exploitation.
Review Worker Process Security: Ensure NGINX worker processes operate with the minimum required privileges. Review process isolation, filesystem permissions, and available security controls to limit the potential impact of successful code execution.
Validate Remediation: Restart affected NGINX services or redeploy updated container images after applying security updates. Verify that patched versions are running, confirm HTTP/2 configurations, and perform targeted vulnerability assessments to ensure remediation is effective.
Organizations should also review F5’s broader November 18, 2026 security release for additional vulnerabilities affecting other NGINX components and configurations.
How Accorian Can Help
Accorian can support your organization in identifying and addressing exposure to these critical NGINX vulnerabilities through vulnerability assessments, application penetration testing, infrastructure security reviews, and security posture assessments.
Our cybersecurity experts can help identify vulnerable NGINX deployments, evaluate internet-facing exposure, prioritize remediation, and assess the effectiveness of existing security controls.
If you suspect suspicious activity or would like assistance evaluating your organization’s exposure to CVE-2026-123633 and CVE-2026-123007, please contact your Accorian representative or schedule a call directly with one of our security experts.
References