F5 has confirmed two code-execution vulnerabilities in Nginx’s HTTP/2 handling. An unauthenticated client can attack the web server itself, even when the application behind it has no corresponding bug. Check the running package and enabled features. Disabling HTTP/2 temporarily blocks these two paths, but does not cover every flaw disclosed alongside them.

Xint’s November 18 disclosure groups five Nginx flaws under “nginx2root.” Wiz independently describes the two HTTP/2 issues. Both teams report controlled code-execution demonstrations. Xint separately reports chaining a Linux kernel flaw to gain host root, including from a Docker container.

Evidence status: vendor-confirmed vulnerabilities and researcher-reported controlled exploitation. The reviewed sources provide no confirmed in-the-wild campaign or victim count. Nginx worker execution, host root and container escape are separate outcomes with different prerequisites.

Two HTTP/2 paths, different conditions

Flaw Exposure confirmed by F5 Fixed Nginx Open Source releases named by F5
CVE-2026-123007 HTTP/2 enabled; faulty flow-control accounting can corrupt worker memory. Affected upstream releases start at 1.9.5 and extend through 1.30.6 and 1.31.8 on their respective branches. 1.30.7 stable; 1.31.9 mainline
CVE-2026-123633 HTTP/2 clients, requests forwarded to a backend, and low available worker_connections. Affected upstream releases start at 1.19.7 and extend through 1.30.6 and 1.31.8. 1.30.7 stable; 1.31.9 mainline

The first flaw can reach ordinary static-file serving in Wiz’s tests; it does not require a backend application. The second uses memory after it has been freed while Nginx is reclaiming connection slots. F5 qualifies code execution on bypassing or disabling memory-address randomization. The researchers report achieving that bypass in their demonstrations.

For Nginx Plus 37.x, F5 names 37.0.8.1 or 37.3.0.1 for CVE-2026-123007. Its earlier fixes for CVE-2026-123633 alone are 37.0.7.1 or 37.2.0.1. A build that fixes only the latter is insufficient for both issues. Consult the product-specific advisory rather than translating Open Source version numbers into Plus versions.

Linux distributions may backport repairs while retaining an older upstream number. Compare the full package revision with the distribution’s advisory. A version banner alone cannot establish patch status.

Ubuntu’s older builds need a separate exposure check. Canonical’s CVE-2026-123633 notes include Ubuntu 16.04–22.04 despite their upstream versions preceding 1.19.7. For those releases, Canonical identifies exposure on cleartext HTTP/2 listeners through the same connection-draining path. Its November 19 security notice lists repaired packages, including 1.18.0-6ubuntu14.23 for 22.04 and 1.24.0-2ubuntu7.20 for 24.04. Compare the full revision for your release.

Update — November 18, 2026, 12:43 p.m. EST

The upstream release rollout has advanced. The Nginx download page now lists 1.31.9 mainline and 1.30.7 stable, with source archives and signatures. Both mainline and stable changelogs date those releases November 18 and explicitly list all five Nginx flaws discussed here.

At the original 10:44 a.m. EST review, those pages still listed 1.31.8 and 1.30.6. That earlier availability caveat is now superseded for upstream source releases. Availability of a repaired package from each distribution or appliance supplier still needs a separate check.

Use your supplier’s verified repair. After installation, restart Nginx or complete its supported live binary upgrade. Nginx’s control documentation distinguishes replacing the executable from reloading configuration.

While a repair is unavailable, Xint and Wiz recommend disabling HTTP/2 on every affected listener. Check legacy listen ... http2 settings as well as the newer http2 directive. Test compatibility first: native gRPC and other HTTP/2-dependent clients may stop working.

Confirm old workers have exited. A configuration reload lets existing clients continue on the old workers. Ending those connections may require a restart, with an interruption to active sessions.

Disabling HTTP/2 leaves other configurations to check

Xint reports three additional, independent Nginx attack paths:

  • CVE-2026-123634, the resolver: request-time backend DNS lookups combined with subrequests. F5 confirms that server-side includes (SSI) or mirroring can reach this issue. Its mitigation avoids those directives and variable-based proxied server names. Disabling mirroring alone can leave an SSI path.
  • CVE-2026-121810, HTTP/3: Xint’s demonstrated path involves forwarding requests to a backend. Its temporary guidance disables the affected HTTP/3/QUIC listeners.
  • CVE-2026-113425, the mail proxy: Xint describes proxy on with auth_http, where login processing reaches the bug before valid credentials are required. Its temporary guidance restricts untrusted access to affected mail listeners.

F5’s disclosure index lists all five. HTTP/3 and mail conditions above are attributed to Xint because the individual F5 pages did not expose their full advisory text during review.

Xint’s separate kernel demonstration requires access to SCTP, a transport protocol implemented in the host kernel. Its success in a tested Docker configuration does not establish that every container can escape. The disclosure gives no kernel CVE identifier or fixed kernel release. Follow distribution guidance separately from the Nginx update.

Investigate suspicious activity without overreading logs

The researchers recommend investigating unexpected worker crashes and commands launched by Nginx workers. Crashes alone have other causes. Xint also warns that the relevant HTTP/2 control traffic need not appear as ordinary requests in access logs. An empty access-log search cannot establish that the server was untouched.

A fronting CDN can change which protocol reaches the origin. Its presence alone is insufficient: exposure depends on whether an attacker can reach the affected Nginx listener and its enabled features.

What the thread adds

The Hacker News discussion adds exploit and patch-availability clarifications:

  • dathery corrects a claim that the flaws require heavy traffic and specific processor features: “There are two bugs here; CVE-2026-123633 does not require a large amount of data or AVX-512.” Rapid7’s approximately 128 GB requirement describes its demonstrated exploit for CVE-2026-123007. Its processor requirements also belong to that exploit strategy. Xint documents the separate connection-draining path for CVE-2026-123633. Do not use the first demonstration’s constraints to dismiss the second flaw.
  • sebiw initially questioned patch availability, prompting the separate download-page check above. The commenter has since added: “Edit: All good. They released the new versions within 30 mins.” The verified upstream release check above remains the basis for availability here.
  • downsplat points to distribution repairs: “If anyone needs it, the Ubuntu package is up”. Canonical’s advisory verifies the package revisions and adds the older-release exposure qualification above.

The thread supplies no confirmed exploitation evidence; forecasts about how soon attacks might start remain speculation. Handles are pseudonymous, and HN exposes no per-comment scores; these selected comments do not establish consensus.

Caveat: Xint and Wiz sell security products. Their exploit demonstrations and kernel-chain results are researcher reports; F5’s advisories establish the product defects and named repairs.