NGINX ( HTTP/2 ) – Critical Remote Code Execution Vulnerability (CVE-2026-123007)
F5 has disclosed a critical vulnerability, CVE-2026-123007, in the HTTP/2 implementation of nginx. The flaw is an integer underflow in HTTP/2 flow-control accounting. A remote, unauthenticated attacker can use this to read and overwrite memory in the nginx worker process and potentially achieve remote code execution, no credentials or user interaction are required.
F5 rates the issue Critical, with a CVSS 4.0 base score of 9.2. It affects nginx Open Source 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8, as well as multiple NGINX Plus releases, in configurations where HTTP/2 is enabled; the vulnerable code has been present since HTTP/2 support was introduced in nginx 1.9.5 in 2015. Servers that support only HTTP/1.1 are not affected. The issue is fixed in nginx Open Source 1.31.9 (mainline) and 1.30.7 (stable), and in NGINX Plus 37.3.0.1 and 37.0.8.1, published on November 18, 2026. No exploitation in the wild has been reported at the time of this notice, but researchers have confirmed working unauthenticated remote code execution against affected builds.
NetSPI Product & Services Coverage
NetSPI EASM: NetSPI’s External Attack Surface Management has released version-based detection for this vulnerability, which will be reported as Vulnerable Version – nginx HTTP/2 RCE (CVE-2026-123007). Because the exact nginx version is not always exposed externally, and because distribution packages may carry a backported fix without changing the reported version, NetSPI also recommends conducting an internal review of any nginx servers.
NetSPI Penetration Testing : NetSPI’s Penetration Testing Services can assist with verifying exposure and validating your patching efforts: NetSPI PTaaS.
Synack CVE Checks : Synack’s CVE catalog has been updated for crowd verification of exposure and patch validation.
Details
| CVE | CVE-2026-123007 | ||||
| Severity | Critical per F5, with a CVSS 4.0 score of 9.2. NVD scoring is pending. | ||||
| Attack Vector | Network – unauthenticated, no user interaction required; reachable only where HTTP/2 is enabled on the nginx server. Note that some factors limit exploitability: code-execution exploit may require significant amounts of HTTP/2 traffic to be transmitted over a single connection, which may fail over slower networks; proxied HTTP/2 connections are unlikely to retransmit the required frames in an exploitable form. | ||||
| Root Cause | Integer Underflow (CWE-191): nginx tracks how much response data an HTTP/2 client has permitted it to send in an unsigned connection counter, h2c->send_window. When a stream is terminated while its DATA frames are still queued, ngx_http_v2_filter_cleanup() returns the reserved credit without checking the HTTP/2 maximum window of 2^31-1, leaving the counter above that limit and ultimately resulting in out-of-bounds reads and writes. | ||||
| Impact | Unauthenticated remote code execution on affected nginx instances with HTTP/2 enabled. Disclosure of worker process memory, including heap and library addresses that defeat address space layout randomization (ASLR). Heap memory corruption leading to worker process crashes and service disruption. Potential access to data handled by the nginx process and to backend systems reachable from the server; because one nginx deployment can front several applications, the impact may extend across multiple services. | ||||
| Affected Products | Vendor advisory (November 18, 2026): nginx Open Source 1.9.5 through 1.30.6 and 131.0 through 131.8 NGINX Plus 37.1.0 through 37.2.0.1 NGINX Plus 37.0.0 through 37.0.7.1 NGINX Plus R34 through R36 Only configurations in which the binary includes the HTTP/2 module and HTTP/2 is enabled on a listening port are exploitable through this path. Linux distribution packages, containers, and third-party products or appliances that bundle nginx with HTTP/2 enabled may also be affected. | ||||
| KEV Status | Not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog as of November 18, 2026 (catalog version 2026.11.18) | ||||
Discovery & Remediation Guidance
- Review and Audit
- Identify all nginx installations in your environment including web servers, reverse proxies, load balancers, containers, and third-party products or appliances that bundle nginx, and confirm the installed version (e.g.
nginx -v). - Confirm whether the binary includes the HTTP/2 module (e.g.
nginx -V 2>&1 | grep -- "--with-http_v2_module"). A binary built without the module is not affected by this vulnerability. - Confirm whether HTTP/2 is enabled in the configuration. Note that
nginx -Treads the configuration on disk, which may differ from the running configuration if it was changed without reloading. - For internet-facing hosts, confirm what is negotiated externally ( e.g.
curl -sI --http2 https://<host>/ | head -1an “HTTP/2” response indicates h2 is enabled ). - Distribution packages may include a backported fix while still reporting an older nginx version. Compare the full installed package version against your distribution’s security advisory rather than relying on the version string alone.
- Monitor for external programs started by the nginx worker account. Review nginx error logs and core dumps for repeated abnormal worker exits or segmentation faults, which may indicate failed exploitation attempts.
- Identify all nginx installations in your environment including web servers, reverse proxies, load balancers, containers, and third-party products or appliances that bundle nginx, and confirm the installed version (e.g.
- Patch Immediately
- Update nginx Open Source to 1.31.9 (mainline) or 1.30.7 (stable), published on November 18, 2026.
- Update NGINX Plus 37.1.0 through 37.2.0.1 to 37.3.0.1, and NGINX Plus 37.0.0 through 37.0.7.1 to 37.0.8.1. F5 lists no fixed release for NGINX Plus R34 through R36; those releases require a move to a supported, fixed branch.
- Restart nginx or complete a supported live binary upgrade after updating. A configuration reload alone does not replace the running executable, and existing HTTP/2 connections remain on old worker processes using the previous configuration.
- The same release also fixes: ( each rated CVSS 9.2, along with several lower-severity issues )
- CVE-2026-123633 (HTTP/2 use-after-free in proxy configurations)
- CVE-2026-121810 (HTTP/3 use-after-free in proxy configurations)
- CVE-2026-123634 (use-after-free in the DNS resolver)
- CVE-2026-113425 (use-after-free in the mail proxy module)
- ^ Review your configuration against all of them; disabling HTTP/2 does not address the other vulnerabilities.
- Mitigation (If Patching Is Delayed)
- On nginx 1.25.1 and later, set http2 off; in each affected server block and remove any legacy http2 parameter from its listen directives, leaving listen 443 ssl;
- On nginx 1.9.5 through 1.25.0, remove http2 from the listen directives, changing listen 443 ssl http2; to listen 443 ssl;
NetSPI Internal Response
NetSPI systems are not affected by CVE-2026-123007. Continuous review, monitoring, and patch validation remain in place.
Additional Resources
Explore More Blog Posts
OpenJDK Base64 Decoder – Critical Memory Corruption Vulnerability (CVE-2026-114938)
A critical memory-corruption vulnerability in OpenJDK's Base64 decoder, tracked as CVE-2026-114938 and nicknamed Java4Shell, may allow a remote attacker to corrupt JVM memory and potentially execute arbitrary code within an affected Java process.
The Attack Path Problem: How Complexity Hides Risk in Financial Services
If you work in financial services, you know the scale of findings isn’t the hardest part. How the findings connect is what really matters. Learn how to pressure-test your security approach against modern AI attacks to your actual environment.
Apache HTTP Server: Critical RCE Vulnerability ( CVE-2026-119618 )
The Apache Software Foundation has disclosed a critical vulnerability, CVE-2026-119618, in the HTTP/2 module (mod_http2) of Apache HTTP Server.