Skip to content
HN On Hacker News ↗

Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007

▲ 1515 points • 644 comments • by speedping • 4d ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this text is a mix of AI and human-written content.

35 %

AI likelihood · overall

Mixed
65% human-written 35% AI-generated
SEGMENTS · HUMAN 13 of 21
SEGMENTS · AI 8 of 21
WORD COUNT 1,395
PEAK AI % 100% · §7
Analyzed
Nov 18
backend: pangram/v3.3
Segments scanned
21 windows
avg 66 words each
Distribution
65 / 35%
human / AI fraction
Verdict
Mixed
Pangram v3.3

Article text · 1,395 words · 21 segments analyzed

Human AI-generated
§1 Human · 0%

Executive SummaryWiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered two critical remote code execution vulnerabilities in NGINX, software used to receive and route traffic to production applications and APIs.NGINX is a common default for the front door of modern web architectures, where it handles HTTPS and routes incoming traffic to the right application or API. As the world's most widely used open-source web server, it powers more than 225 million websites.Successful exploitation could let attackers take control of affected NGINX servers, steal sensitive data, tamper with websites, or disrupt services.The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2.

§2 Human · 0%

The flaws are in NGINX itself.

§3 Human · 0%

Websites and APIs can be exposed even when their own application code is secure.

§4 Human · 0%

Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server.

§5 Human · 0%

Additional conditions are described below.

§6 Human · 0%

CVE-2026-123007 affects versions dating back to NGINX 1.9.5 in 2015.We reported our findings to F5, the company behind NGINX, and collaborated with its security team on remediation and coordinated disclosure. Organizations should identify affected deployments and apply the security updates when released.We recommend updating affected NGINX deployments to the latest release which includes multiple security fixes.Responsible disclosure timelineOctober 21, 2026: Wiz reports the HTTP/2 use-after-free vulnerability, later assigned CVE-2026-123633, to F5, including confirmed remote code execution with an ASLR bypass and a proposed fix. F5 confirms that another research team had previously reported the same vulnerability.November 10, 2026: F5 supplies a patch for CVE-2026-123633 for review.November 16, 2026: Wiz reports the second HTTP/2 vulnerability, later assigned CVE-2026-123007, to F5.November 17, 2026: F5 confirms that the second report matches CVE-2026-123007 and is included in the planned November 18 security release.November 18, 2026: F5 security release and coordinated public disclosure.OverviewWiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered  CVE-2026-123633 and CVE-2026-123007, two critical unauthenticated remote code execution vulnerabilities in NGINX, and reported them to F5, the company behind NGINX. Successful exploitation can compromise the server running NGINX, allowing attackers to execute code, steal sensitive data, tamper with websites, or disrupt services.NGINX often handles traffic for several applications, so a single affected deployment can put multiple services at risk. The flaws are in NGINX itself and can affect websites even when their own application code is secure. Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server. Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.Wiz Research used Wiz Atlas, the harness powering Wiz’s AI Code scanning solution, to discover both vulnerabilities. Our researchers used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate the impact of both vulnerabilities, confirming that each could allow an unauthenticated attacker to execute code on the server. We reported our findings to F5 and worked with its security team on remediation and coordinated disclosure.The integer underflow vulnerability dates back to NGINX 1.9.5 in 2015, meaning it had been hiding in the code for more than a decade. The use-after-free vulnerability had been there for nearly six years. Like the PHP2Shell vulnerabilities we reported last month and Java4Shell, disclosed yesterday by Calif, these are memory-safety flaws that have historically been extremely difficult to discover and exploit.

§7 AI · 100%

Finding them often requires tracing subtle interactions between memory operations and multiple code paths. For years, that complexity itself created a practical barrier.

§8 AI · 87%

AI is fundamentally dissolving that barrier.

§9 Human · 0%

As AI models get better at following those interactions, both researchers and attackers can uncover longstanding flaws in software that powers the internet and modern applications. The fact that multiple independent research teams uncovered the same vulnerabilities in both PHP and NGINX, after they had remained in the code for years, makes this shift particularly striking.

§10 AI · 100%

And as AI capabilities advance, each new generation of models may uncover even more complex vulnerabilities that were previously beyond practical reach. Complexity can no longer be relied upon as a barrier to discovery or exploitation. This changes not only which vulnerabilities can be found, but how quickly longstanding risks can become real threats.Over time, finding and fixing these flaws can harden the software we all depend on. In the near term, faster discovery and a shorter window between disclosure and exploitation add to an already demanding workload for security teams. Turning a published fix into protection in production still takes substantial manual work, from validating patches to coordinating rollouts with service owners.

§11 AI · 100%

We recommend focusing on how quickly you can reduce exposure in production.

§12 AI · 95%

Identify deployments running the affected version and configuration, prioritize those an attacker can reach, and apply mitigations while patches are tested and rolled out.In this post, we explain the vulnerabilities and their impact, and provide mitigation and detection guidance.

§13 Human · 0%

Organizations should identify affected deployments and apply the security updates as soon as they are available.

§14 Human · 0%

If upgrading is not immediately possible, temporarily disable HTTP/2.What is NGINX?NGINX is the world's most widely used open-source web server, powering more than 225 million websites. It is commonly used as a reverse proxy in front of websites and APIs. In this role, NGINX accepts incoming requests, forwards them to the appropriate application server based on its configuration, and returns the response to the user.NGINX can also serve web content directly and act as a load balancer, distributing traffic across multiple servers. A single NGINX deployment can serve several applications, making it a shared entry point for the websites and APIs behind it.The VulnerabilitiesBoth vulnerabilities are memory-safety issues in how NGINX handles HTTP/2 traffic.

§15 Human · 0%

In CVE-2026-123633, a connection's memory is freed while a request still needs it, creating a use-after-free. In CVE-2026-123007, incorrect flow-control accounting leads to an invalid memory copy.

§16 Human · 0%

Each can lead to unauthenticated remote code execution on the NGINX server.Tracking IDThe bugWhat an attacker can achieveCVE-2026-123633HTTP/2 connection use-after-freeExecute arbitrary code on the NGINX server without authentication.CVE-2026-123007HTTP/2 send_window integer underflowExecute arbitrary code on the NGINX server without authentication.Both vulnerabilities require HTTP/2 to be enabled, but their additional requirements differ. CVE-2026-123633 affects reverse-proxy processing when available connection slots run low. CVE-2026-123007 can also affect NGINX serving content directly, as demonstrated in our testing over HTTPS on 64-bit systems. Typical memory safety mitigations such as ASLR do not protect against these issues, as attackers can use either vulnerabilities for memory read access prior to code execution.ImpactOn affected NGINX versions with HTTP/2 enabled, these vulnerabilities can allow an unauthenticated attacker to execute arbitrary code on the server.The flaws are in NGINX itself.

§17 AI · 100%

Exploitation does not depend on a bug in the website or API behind it, so applications with secure code can still be exposed. For CVE-2026-123007, we demonstrated remote code execution on a server serving ordinary static files, without a backend application or third-party module.An attacker could use this access to run commands, steal sensitive data, tamper with websites, or disrupt services.

§18 AI · 100%

Because one NGINX deployment can serve several applications, the impact could extend across multiple websites and APIs.Illustrative deployment: an attacker exploits NGINX to run code on the server, putting the applications and data it serves at risk.Coordinated disclosureWe reported both vulnerabilities to F5 and collaborated with its security team on remediation and coordinated disclosure.

§19 Human · 1%

We also shared proposed fixes.

§20 Human · 0%

Ikotas Labs, Metnir, Rapid7, and Xint also independently discovered and reported these issues to F5. We thank the F5 and NGINX teams for their work on the fixes.Mitigation and detectionIdentify affected NGINX deployments with HTTP/2 enabled and upgrade to a release that fixes both vulnerabilities as soon as it is available.ProductCVE and first affected version or branchFixed releasesNGINX OSSCVE-2026-123633: 1.19.71.30.7 stable; 1.31.9 mainlineNGINX PlusCVE-2026-123633: R33; 37.0.037.0.7.1; 37.2.0.1NGINX OSSCVE-2026-123007: 1.9.51.30.7 stable; 1.31.9 mainlineNGINX PlusCVE-2026-123007: R33; 37.0.037.0.8.1; 37.3.0.1If you cannot upgrade immediately, temporarily disable HTTP/2 on affected NGINX instances:Set http2 off; in affected server blocks on NGINX 1.25.1 or later, and remove the http2 parameter from any listen directives.Test application compatibility, reload NGINX, and confirm the old workers have exited.Re-enable HTTP/2 after upgrading.Investigate unexpected NGINX worker crashes or commands launched by NGINX; these are general warning signs, not confirmed indicators of these vulnerabilities.Technical deep diveCVE-2026-123633: An active connection marked as reusableNGINX keeps a list of connections that it can close when it needs room for new ones.

§21 AI · 100%

An HTTP/2 connection can join this list when it has no active requests, but must leave it when a request starts.We start by sending only part of a HEADERS frame, which carries an HTTP/2 request's headers.