Wednesday, November 18, 2026Vol. III · No. 322Subscribe
The Mining, Energy & Technology Wire

Nginx HTTP/2 RCE Vulnerability Patched

Five research teams independently found critical unauthenticated flaws in NGINX's HTTP/2 handling, and F5 has shipped emergency patches.

Nginx HTTP/2 RCE Vulnerability Patched
PhotographFive research teams independently found critical unauthenticated flaws in NGINX's HTTP/2 handling, and F5 has shipped emergency patches.Photo: Musfiqur Ehsan / Unsplash

F5 released emergency patches for 10 bugs in open source NGINX on Wednesday, Nov 18, 2026, among them a critical Nginx HTTP/2 RCE vulnerability that five separate research teams found independently, The Register reported. Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint all uncovered critical remote code execution flaws in the web server, according to Wiz.

The scale of exposure is what turns a patch note into a headline. NGINX powers around 225 million websites, The Register reported, and F5 maintains the open source version. Wiz puts the figure at more than 225 million websites. An unauthenticated attacker, meaning one with no login or prior access, can reach the vulnerable code simply by connecting to a server with HTTP/2 enabled.

What exactly did researchers find in NGINX?

Two of the bugs carry the most weight. Wiz says they are tracked as CVE-2026-123633 and CVE-2026-123007, both rated Critical with a CVSS 4.0 score of 9.2. Both require HTTP/2 to be enabled on the affected server, Wiz said.

CVE-2026-123633 is an HTTP/2 use-after-free flaw. Wiz says it reported that bug to F5 on October 21, 2026, and F5 confirmed another research team had already reported the same vulnerability. Xint's timeline, in Korea Standard Time, says its team discovered its set of vulnerabilities on Oct 11, 2026 and reported them to F5 through HackerOne on Oct 16, 2026.

CVE-2026-123007 is a different animal. Rapid7 describes it as a critical integer underflow affecting nginx HTTP/2 that can allow unauthenticated remote code execution against affected servers under certain conditions. Stephen Fewer, Senior Principal Security Researcher at Rapid7, discovered it, according to the company. Xint independently says one of its researchers found CVE-2026-123007 while preparing for ZeroDay Cloud 2026.

Wiz's own testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, with no backend application and no third-party modules involved. That matters because it describes a plain, default-looking deployment rather than an exotic configuration.

How much does an attacker actually need?

The practical hurdles are real, and Rapid7 spelled them out. Leveraging CVE-2026-123007 for remote code execution requires approximately 128 GB of HTTP/2 data to be transmitted, the company said. In its demonstration, exploitation takes two and a half minutes. A network slower than approximately 300 Mbit/s will exceed nginx's default one hour connection lifetime and fail.

Rapid7 also says its exploitation strategy depends on a specific x86-64 glibc EVEX/YMM memcpy implementation, selected at runtime based on the avx512f and avx512vl CPU features. Those are narrow conditions. They are not a guarantee of safety, though, and Xint's demonstrations point the other way. The Register reported that Xint's videos show attacks using CVE-2026-123007 working on AWS, Microsoft Azure, Google Cloud Platform and bare-metal servers.

Code run through the flaw gets the permissions of an NGINX worker process, The Hacker News reported. That is not the end of the chain. In Xint's tests, code running as a worker could get root on the host through a separate bug in the Linux kernel's SCTP code, even when NGINX ran inside a Docker container, The Hacker News said.

As for active attacks, The Hacker News reported that neither the vendor nor the Wiz and Rapid7 researchers have reported any attacks exploiting the flaw so far.

Why did five teams find the same bug?

AI is the common thread. The Register reported that the critical NGINX bugs were uncovered by researchers using AI, as were other recently disclosed vulnerabilities in foundational technologies like PHP, Apache and Java.

Wiz says Wiz Research used Wiz Atlas, the harness powering its AI Code scanning solution, to discover both vulnerabilities. Xint's account is starker. It says that after one researcher found CVE-2026-123007, a fully automated Xint scan found the other four a few days later without human guidance. Xint calls the full set nginx2root, a collection of 5 critical CVEs, the most impactful of which allows an unauthenticated attacker to execute commands on an affected nginx server with HTTP/2 enabled.

Xint also described what finding such a bug has meant historically: an unauthenticated remote code execution bug in nginx "has long been a holy grail for security researchers."

The pattern extends beyond NGINX. The Register reported that Tuesday's Java4Shell was found by AI-bug-hunting outfit Calif, one of the firms that also used AI to find and weaponize the critical PHP vulnerabilities known as PHP2Shell. Tomer Schwartz, Wiz's chief technology officer of exposure management and AppSec, who helped find the NGINX bug, told The Register:

"We need to treat every internet-connected system as potentially vulnerable."

The advisory list itself shows the change in tempo. Xint says the nginx security advisory list recorded two new vulnerabilities the year before and 26 by November 17 this year, not counting nginx2root.

Which servers are exposed, and what is the fix?

Xint tried to size the internet-facing population. As of November 10, 2026, Shodan returned 56.7 million hosts for product:nginx, of which 11.94 million (21.1%) reported an identifiable version. The rest do not advertise what they run, which complicates any attempt to count the vulnerable.

The patched releases fix more than the headline pair. The Hacker News reported that the same releases fix four more flaws the vendor says can lead to code execution under the same ASLR condition, and that F5 scores all five 9.2 out of 10 on CVSS 4.0. Disabling HTTP/2 is not a full answer. Xint says it blocks CVE-2026-123007 and CVE-2026-123633 but does not block the other three nginx vulnerabilities.

One gap stands out. For NGINX Plus R34 to R36, The Hacker News reported, there is no fix listed.

What Changed This Week

F5 shipped emergency patches for 10 NGINX bugs on Nov 18, 2026, including a pair of critical HTTP/2 flaws scored 9.2 on CVSS 4.0. Five teams reached the core bugs independently, using AI tooling in at least two cases, and Xint says an automated scan alone turned up four of its five. Researchers have shown code execution on plain static-file servers, demonstrated attacks across major clouds, and shown a path from worker process to root in one test setup. No exploitation in the wild has been reported.

What to Watch

Watch first for any report of active exploitation, since the vendor and the Wiz and Rapid7 researchers had reported none at the time of The Hacker News' coverage. Watch also for whether F5 lists a fix for NGINX Plus R34 to R36, where none is currently listed. And keep an eye on the pace of AI-assisted disclosures in foundational software: The Register has already tied PHP, Apache and Java disclosures to the same methods, and the NGINX advisory list is moving much faster than it did the year before.


Reporting based on coverage from The Register, Wiz Security, The Hacker News, Rapid7 and XINT, November 2026.

Original reporting and analysis by the Stake & Paper editorial team. See linked sources within the article.

Share this story

More from Stake & Paper

Was this article helpful?

ClaimWatch

Mining claims intelligence — from query to report, in minutes.

Every unpatented mining claim across all twelve BLM states. Leadfile audits, due diligence, site selection, regional prospecting, entity investigations, and AOI monitoring — delivered as complete report packages.

4.4M+
Claims Tracked
12
BLM States
7
Report Types
Request a Sample Report
Stake & Paper AM

One morning brief. The whole energy sector.

Original analysis, the day's most important wire stories, and market data — delivered before your first cup of coffee. Free.