Skip to content
AI Security Wire

Published

- 6 min read

By

NGINX HTTP/2 RCE: CVE-2026-123633 and CVE-2026-123007 Patched

img of NGINX HTTP/2 RCE: CVE-2026-123633 and CVE-2026-123007 Patched

F5 released NGINX 1.30.7 and 1.31.9 on November 18, 2026 to fix two HTTP/2 flaws that Wiz demonstrated as unauthenticated remote code execution. CVE-2026-123633 is a use-after-free and, per Wiz, CVE-2026-123007 is an integer underflow in flow-control accounting. F5’s CVSS v4.0 score for both is 9.2 (Critical), and Wiz calls them critical. The nginx.org advisory list rates 123633 “medium” and 123007 “major”. Wiz says five teams (Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint) independently found them. F5’s CVE credits name six reporters split across the two CVEs, including Palo Alto Networks Unit 42 for 123633. Wiz says its team used an AI vulnerability research harness.

What was disclosed

FieldCVE-2026-123633CVE-2026-123007
Bug (per Wiz)Use-after-free of an HTTP/2 connectionsend_window integer underflow
Affected (NGINX OSS, per Wiz; fixed in 1.30.7 and 1.31.9)1.19.7 to 1.31.81.9.5 to 1.31.8
CVSS v4.0 (F5 as CNA, secondary)9.2 Critical9.2 Critical
CVSS v3.1 (F5 as CNA, secondary)8.1 High8.1 High
nginx.org severitymediummajor
PreconditionHTTP/2 enabled, NGINX acting as a reverse proxy, workers low on worker_connections (per F5 CVE text)HTTP/2 enabled

As of our check on November 19, NVD showed no NVD-assigned score for either record. The scores above come from F5, the CNA, and are labelled secondary for that reason. In our reading, the gap between 9.2 and 8.1 comes from the two scoring systems, not a disagreement over severity. Both vectors carry high attack complexity.

How the bugs work

CVE-2026-123633. Per Wiz, NGINX marks an HTTP/2 connection as reusable, meaning it can be closed to free a connection slot, when it has no active requests. A client sends only part of a HEADERS frame, so the connection is marked reusable while NGINX waits. When the rest arrives, a request stream is created but the connection is never removed from the reusable list. If the request is forwarded upstream when free connection slots are scarce, NGINX can select that same connection for closing. If the GOAWAY notification then fails, for example because the per-connection frame limit is reached, the error path frees the connection memory while the request still uses it.

CVE-2026-123007. NGINX tracks the allowance for outgoing response data in h2c->send_window. When a stream is canceled with data still queued, a cleanup routine refunds the unused allowance without checking HTTP/2’s maximum window. If the client had already raised the window, the counter can exceed the maximum. A later bounds check subtracts the counter from the maximum using an unsigned integer, so it wraps to a large value and passes. The oversized counter is later converted to a signed type, becomes negative, and produces a malformed buffer that the TLS send path copies out of bounds. Wiz reports remote code execution with an ASLR bypass on official 1.31.7 and 1.31.8 builds, using HTTP/2 over TLS on 64-bit systems, against NGINX serving ordinary static files with no backend application or third-party module.

Exploitation status

F5’s CVE text says exploitation may allow denial of service or code execution, with code execution conditional on ASLR being disabled or bypassed. Wiz and Xint demonstrate code execution. Wiz says it built proof-of-concept exploits and ran them in lab settings but will not release them “at this time”. It cautions that reliable remote exploitation of memory-safety bugs needs memory disclosure, heap grooming and per-build handling, and that attackers could focus first on packaged products where many deployments share one build. Rapid7 has published a proof-of-concept repository for CVE-2026-123007, so public exploit code exists for that flaw. Its README says it is only suitable to demonstrate this RCE approach against a freshly started local Docker container and will likely fail against a server with multiple concurrent clients or a messy heap layout. Xint has published demo videos.

On in-the-wild activity, we found no report as of November 19 in the sources below. An F5 spokesperson told The Register there was no evidence of exploitation, and neither CVE was in the CISA Known Exploited Vulnerabilities catalog (latest release 2026-11-18 19:17 UTC, checked November 19). CISA coordinator SSVC entries in NVD, timestamped November 18, list exploitation as none. Those are point-in-time statements. Our assessment is that public proof-of-concept code, even a limited one, makes probing for CVE-2026-123007 a plausible near-term possibility, and defenders should not wait for a KEV listing.

Scope of the release

The F5 release fixes 10 CVEs in total. Wiz lists three more at CVSS 9.2: CVE-2026-121810 (HTTP/3 use-after-free), CVE-2026-123634 (DNS resolver use-after-free) and CVE-2026-113425 (mail proxy use-after-free), each tied to a specific configuration (nginx.org rates 121810 and 123634 “medium” and 113425 “major”). Xint’s separate write-up describes five remote code execution paths and a chained kernel flaw, and says disabling HTTP/2 mitigates only CVE-2026-123007 and CVE-2026-123633. Treat the workaround as a stopgap, not a substitute for the update. Xint warns that distribution packages may backport fixes without changing the version string, so confirm the fix through your distro’s advisory.

Defensive guidance

  1. Inventory NGINX instances, including those inside container images, ingress controllers and appliances, and note which have http2 enabled.
  2. Upgrade to 1.30.7 or 1.31.9 (NGINX Plus builds listed in the FAQ). Prioritize any internet-facing HTTP/2 listener, reverse proxies first, since they can be exposed to both flaws.
  3. If you cannot upgrade, set http2 off; per server block on 1.25.1 or later (on older versions, remove http2 from listen directives), reload, and confirm old workers exited. Test application compatibility first.
  4. Alert on unexpected worker crashes and on processes launched by NGINX. Wiz describes these as general warning signs, not confirmed indicators for these CVEs. For CVE-2026-123007, long-lived HTTP/2 connections sending many WINDOW_UPDATE frames and large volumes of data may be worth a detection rule.
  5. If a CDN or WAF terminates HTTP/2 in front of NGINX, Wiz says it may blunt parts of the exploit. That depends on the implementation, so do not rely on it.

The wider pattern matters too. Wiz links these findings to its PHP2Shell work last month and says AI is shortening the path to long-standing memory-safety bugs, with a shorter window between disclosure and exploitation. The CVE-2026-123007 flaw dates to NGINX 1.9.5 in 2015, according to Wiz.

References

Frequently Asked Questions

Which NGINX versions fix CVE-2026-123633 and CVE-2026-123007?
NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). Per Wiz's table, NGINX Plus fixes are 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007. Wiz lists the affected open source range as 1.19.7 to 1.31.8 for CVE-2026-123633 and 1.9.5 to 1.31.8 for CVE-2026-123007.
Are these flaws being exploited in the wild?
We found no report of in-the-wild exploitation as of November 19, 2026. An F5 spokesperson told The Register there was no evidence of exploitation, and neither CVE appeared in the CISA Known Exploited Vulnerabilities catalog (latest release 2026-11-18 19:17 UTC, checked November 19), and the CISA coordinator SSVC entries in NVD list exploitation as none. Wiz says it built working proof-of-concept exploits but is not releasing them. Rapid7 has published a proof-of-concept repository for CVE-2026-123007, so exploit code is public.
Can I mitigate without upgrading?
Yes, partly. Both flaws need HTTP/2 enabled, so Wiz advises setting http2 off in affected server blocks (NGINX 1.25.1 or later) and removing the http2 parameter from listen directives, then reloading and confirming old workers have exited. In our reading it does not address the other CVEs in the same release, and Xint says three of its five RCE paths are not blocked by disabling HTTP/2.