Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Censys Research graphic titled 5.69 MB. One clear HTTP/2 difference, comparing the frame sequence accepted by vulnerable nginx 1.31.8 with the patched 1.31.9, which rejects the window update and logs a flow-control violation.
Image: Censys (fair use). Summary graphic from the Censys ARC report "nginx2root: A simple test for the HTTP/2 flaw and three use-after-free reproductions," published Nov. 18, 2026.

Response

Censys Says Turning Off HTTP/2 Covers Only Two of the Five nginx2root Flaws, and Publishes a 5.69 MB Test That Tells Patched nginx From Vulnerable

The internet scanning firm reproduced four of the five nginx bugs disclosed this week, released packet captures and a candidate Suricata rule, and counted about 8.8 million internet-facing nginx services still on an affected version with HTTP/2 enabled.

Noah Park, ResponseNew York5 min read

NEW YORK - Security teams that disabled HTTP/2 as a stopgap after this week's nginx disclosures have closed only part of the exposure, researchers at the internet scanning company Censys said, after reproducing four of the five memory-safety flaws in a lab and publishing a small test that lets defenders confirm whether a server is patched.

The five vulnerabilities, which the research firm Xint disclosed on Wednesday under the name nginx2root, each corrupt memory in an nginx worker process, but each needs a different feature to be reachable: HTTP/2, reverse proxying over HTTP/2 or HTTP/3, runtime DNS resolution with subrequests, or mail proxy authentication. "Disabling HTTP/2 addresses only two of the five nginx CVEs," Censys wrote, adding that full patching is required.

SOCtember reported on Wednesday on the two HTTP/2 flaws, CVE-2026-123633 and CVE-2026-123007, and the interim advice to turn HTTP/2 off. The other three are CVE-2026-123634, in the resolver when a proxied server name contains variables and an SSI or mirror subrequest resolves the same name; CVE-2026-121810, affecting HTTP/3 configurations; and CVE-2026-113425, affecting nginx configured as a mail proxy. Xint said each can be chained with a separate Linux kernel bug to gain root, a claim Censys said it has not verified.

A small test instead of 100 GB of traffic

Rapid7's public proof of concept for CVE-2026-123007 needs very large volumes of HTTP/2 traffic to reach its crash and code execution stages; Censys put the reported figure at 60 to 119 GiB. Censys built a compact cleartext HTTP/2, or h2c, test that reaches the corrupted flow-control state and produces different responses from vulnerable nginx 1.31.8 and patched 1.31.9. The full capture is 5.69 MB. On the vulnerable build, a stream reset followed by a one-byte window update is accepted; the patched build rejects the update and logs a flow-control violation.

The company was careful about what that proves. The test confirms the accounting error, Censys said, but "does not itself demonstrate code execution." The test, the packet captures and lab evidence for each CVE are published in a public GitHub repository.

Screenshot of the Censys table What Censys ARC confirmed, listing each nginx2root CVE, its attack path and lab result: an accounting error confirmed for CVE-2026-123007, a use-after-free and worker crash for CVE-2026-123633, use-after-free under AddressSanitizer for CVE-2026-123634, a stale-session crash for CVE-2026-113425, and CVE-2026-121810 not reproduced.
Image: Censys (fair use).Lab results for each of the five CVEs, from the Censys report.

Censys also reproduced use-after-free conditions for three of the other four bugs, none of which produced code execution in its lab. CVE-2026-123633 crashed a worker on the unmodified official 1.31.8 image. CVE-2026-113425 caused a stale-session crash on a pristine 1.31.8 build. CVE-2026-123634 was confirmed under AddressSanitizer and crashed a custom debug build but not the stock image. The HTTP/3 flaw, CVE-2026-121810, was not reproduced.

What a detection can and cannot see

For network teams, the report sets limits. The relevant HTTP/2 control frames are hidden by TLS, so payload signatures need decrypted telemetry or cleartext h2c. Large WINDOW_UPDATE frames, stream resets, GOAWAY frames and dropped workers all occur in normal traffic and do not on their own indicate exploitation, Censys said.

Its candidate Suricata rule, signature ID 9007015, fired exactly once on the vulnerable capture and not at all on the patched control on Suricata 8.0.1. Censys described that as validation against one traffic pair, not a general exploit detector. Its other rules passed 16 synthetic scenarios, but single-byte TCP segmentation exposed a gap in the raw-stream signatures, and the rules for Rapid7's bootstrap sequence have not been tested on live traffic.

Screenshot of the Censys ARC Nginx2root services dashboard, updated 08:06 UTC on Nov. 19, showing 9,233,681 nginx services seen on an affected version with HTTP/2 since Nov. 18, 8,794,135 still exposed at their most recent scan, and 417,553 since seen on a fixed release or without HTTP/2.
Image: Censys (fair use).The Censys ARC nginx2root exposure dashboard, captured Nov. 19, 2026.

Censys's public dashboard put the scale in view on Thursday morning. As of its 08:06 UTC update, it had seen 9,233,681 nginx services on an affected version with HTTP/2 since tracking began on Nov. 18, and 8,794,135 were still in that state at their most recent scan. Only 417,553 had since been seen on a fixed release or with HTTP/2 off. Those counts rely on version banners and cover only the HTTP/2 path, so they say nothing about the resolver, HTTP/3 or mail proxy configurations.

As of 2 p.m. Pacific time on Wednesday, Censys said it was not aware of exploitation in the wild, and none of the five CVEs was in CISA's Known Exploited Vulnerabilities catalog, which it called "a point-in-time absence of evidence, not proof that no attacks have occurred."

What response teams should do

The fixes are nginx Open Source 1.30.7 or later on the stable branch and 1.31.9 or later on mainline, and NGINX Plus 37.0.8.1 or 37.3.0.1. Censys stressed that a configuration reload does not replace the running binary, so the service must be fully restarted, and that teams using distribution packages should confirm the vendor advisory covers all five CVEs.

Screenshot of the Censys-Research nginx2root repository on GitHub, with folders for each CVE, evidence, a test suite and documentation, described as isolated-lab reproductions of the five nginx2root vulnerabilities.
Image: Censys via GitHub (fair use).The public repository holding the h2c test, captures and per-CVE lab evidence.

Beyond patching, the company advised auditing for HTTP/2 and HTTP/3 listeners, dynamic resolver settings, request-driven proxying, subrequests and mail proxy auth_http rather than relying on version banners; restricting mail proxy traffic to trusted sources; and noting that mirror_request_body on does not fully remove the subrequest risk. For SOC teams, it recommended keeping nginx error logs, worker crash events and HTTP/2 flow-control errors with timestamps and listener details, treating unexpected child processes or outbound connections from nginx workers as high-priority events, and not declaring a compromise on crashes or resets alone.

About the Author

Noah Park

Noah Park covers incident response, containment, and blue-team operations for SOCtember from New York.

Related stories

Response desk