
A critical vulnerability in NGINX’s HTTP/2 module could allow remote attackers to trigger memory corruption, crash worker processes, and potentially execute arbitrary code on vulnerable web servers.
Tracked as CVE-2026-123007, the vulnerability affects NGINX Open Source and NGINX Plus configurations using HTTP/2. The issue is caused by an integer underflow in HTTP/2 flow-control processing, potentially resulting in a heap buffer overflow and an out-of-bounds memory write.
F5 disclosed the vulnerability on November 18, 2026, and released software updates addressing the issue. Security teams are urged to prioritize patching exposed NGINX deployments, particularly systems handling HTTP/2 traffic from untrusted clients.
Vulnerability details
CVE-2026-123007 is associated with improper handling of HTTP/2 flow-control window values within the ngx_http_v2_module component.
When NGINX processes specially crafted traffic, the flow-control window can exceed permitted limits. This may trigger an integer underflow and result in heap memory corruption, potentially causing an NGINX worker process to crash.
Under certain conditions, attackers may be able to leverage the memory corruption to execute arbitrary code remotely. F5 notes that code execution is possible on systems where Address Space Layout Randomization (ASLR) is disabled or where an attacker can bypass ASLR protections.
Successful exploitation could compromise the confidentiality, integrity, and availability of services handled by the affected NGINX instance.
The vulnerability is remotely exploitable without authentication, although exploitation is considered to require additional complexity.
Affected systems
According to F5, the vulnerability affects the following versions when HTTP/2 is enabled:
- NGINX Open Source: Versions 1.9.5 through 1.30.6.
- NGINX Open Source mainline: Versions 1.31.0 through 1.31.8.
- NGINX Plus: Versions 37.0.0 through 37.0.7.1.
- NGINX Plus: Versions 37.1.0 through 37.2.0.1.
The vulnerability affects the ngx_http_v2_module component. Deployments that do not use HTTP/2 are not affected by this specific vulnerability.
F5’s advisory lists NGINX Plus R34 through R36 as not affected, while other F5 products listed in the advisory are not currently identified as vulnerable to CVE-2026-123007.
Administrators should review the official advisory carefully, particularly when operating vendor-maintained builds, container images, or software packages that may include backported security fixes.
Severity and exploitation risk
F5 assigns the vulnerability a CVSS score of 8.1 (High) under CVSS v3.1 and 9.2 (Critical) under CVSS v4.0, highlighting the potential severity of successful exploitation.
The vulnerability can potentially be exploited remotely without authentication, with impacts including denial of service, memory corruption, and remote code execution under certain conditions.
Security researchers have reportedly demonstrated exploitation, and proof-of-concept code has been publicly reported. Although confirmed exploitation in the wild has not been reported in the cited advisories, the availability of public exploit research increases the risk of attacks against unpatched internet-facing servers.
Organizations should treat exposed vulnerable NGINX instances as high-priority remediation targets.
Security updates released
F5 has released patched versions of NGINX Open Source and NGINX Plus.
The following versions address CVE-2026-123007:
- NGINX Open Source stable: Upgrade to version 1.30.7.
- NGINX Open Source mainline: Upgrade to version 1.31.9.
- NGINX Plus 37.x: Upgrade to version 37.3.0.1 or 37.0.8.1, depending on the applicable branch.
Administrators should consult F5’s official advisory to select the correct fixed release for their deployment and verify whether vendor-specific security updates are available.
Recommended mitigation measures
Organizations running vulnerable NGINX installations are advised to take the following actions:
- Identify all NGINX Open Source and NGINX Plus deployments across their infrastructure.
- Determine whether HTTP/2 is enabled on internet-facing services.
- Upgrade vulnerable installations to the appropriate fixed version immediately.
- Restart or reload NGINX as required to ensure patched binaries and modules are active.
- Review container images, reverse proxies, ingress controllers, and third-party products that bundle NGINX.
- Prioritize systems exposed directly to untrusted internet traffic.
- Verify that ASLR and other operating-system memory protections are enabled.
If immediate patching is not possible, administrators may temporarily disable HTTP/2 to reduce exposure to this vulnerability. This should be treated as a temporary risk-reduction measure rather than a replacement for installing the security update.
Detection and threat hunting
Security teams should monitor NGINX systems for unusual behavior that could indicate exploitation attempts or successful compromise.
Potential indicators include:
- Unexpected NGINX worker crashes or segmentation faults.
- Repeated abnormal HTTP/2 connections or suspicious request patterns.
- Unusual child processes spawned by NGINX workers.
- Unexpected outbound network connections from web server processes.
- Unauthorized modifications to web application files, configuration files, or system resources.
- New scheduled tasks, persistence mechanisms, or suspicious executables appearing on the server.
Organizations should investigate suspicious activity, preserve relevant logs and forensic evidence, and isolate potentially compromised servers when necessary.
If remote code execution is suspected, administrators should consider the server compromised, investigate the extent of potential access, rotate exposed credentials and secrets, and rebuild affected systems from trusted sources where appropriate.
Conclusion
CVE-2026-123007 highlights the security risks associated with memory corruption vulnerabilities in widely deployed web server infrastructure. The flaw affects NGINX HTTP/2 processing and could allow remote attackers to disrupt services or potentially execute arbitrary code on vulnerable systems.
With patches available and public exploit research reportedly emerging, organizations should not delay remediation. Updating NGINX, reviewing HTTP/2 exposure, monitoring for suspicious activity, and strengthening server security controls are essential steps to reduce the risk of compromise.
Official security advisory: F5 – NGINX ngx_http_v2_module vulnerability CVE-2026-123007
