NGINX HTTP/2 RCE now refers to two distinct flaws disclosed on November 18, 2026: CVE-2026-123007 and CVE-2026-123633. Both affect NGINX’s HTTP/2 data plane, but their triggering conditions and NGINX Plus patch paths differ. F5 rates each 8.1 High under CVSS 3.1 and 9.2 Critical under CVSS 4.0.
The immediate task is to identify servers accepting HTTP/2, determine their installed branch, and match each deployment to both fixes. The comparison below uses the F5 CNA record for CVE-2026-123007 and the F5 CNA record for CVE-2026-123633. F5 has not evaluated versions past End of Technical Support in those records.
NGINX HTTP/2 RCE: Which Patch Path Covers Each CVE?
- Fixed
The shared OSS releases make the open-source update straightforward: 1.30.7 on stable or 1.31.9 on mainline covers both records. NGINX Plus needs closer attention because the CVE-2026-123007 fix comes later on each listed 37.x path. For Plus 37.0, reach 37.0.8.1; for the newer path, reach 37.3.0.1 to cover both.
F5 lists older affected starting points separately. CVE-2026-123007 reaches back to OSS 1.9.5, while CVE-2026-123633 starts at OSS 1.19.7. Both records include NGINX Plus from R33, and older unsupported versions were not evaluated. Check the distribution’s vendor package advisory when NGINX is supplied through an operating system, since package version strings can differ from upstream release numbers.
What Makes the Two HTTP/2 Flaws Different?
CVE-2026-123007 concerns HTTP/2 flow-control accounting. According to Wiz Research’s analysis, an invalid counter can reach a memory-copy path and cause memory disclosure or corruption. Wiz demonstrated code execution in a lab on official 1.31.7 and 1.31.8 builds serving ordinary static files over HTTP/2 and TLS. That test did not require a backend application or a third-party NGINX module.
CVE-2026-123633 is a use-after-free in an HTTP/2 worker connection. F5 says the server must proxy client requests to a backend while the worker runs low on available worker_connections. The proxy request can then interact with a connection still marked reusable, according to Wiz. A static-content server does not meet the proxy condition F5 describes for this CVE.
For both records, F5 describes possible code execution when ASLR is disabled or an attacker can bypass it. Wiz reports an ASLR bypass in its laboratory research, but that does not make every exposed build equally exploitable. Neither CVE is a flaw in the application code behind NGINX. Their shared HTTP/2 requirement is the first configuration question for the asset owner.
Three other NGINX disclosures describe different conditions. CVE-2026-113425 concerns mail proxy operation; CVE-2026-121810 concerns HTTP/3. CVE-2026-123634 requires a variable upstream name plus an SSI or mirror subrequest that resolves the same name. Do not treat those records as additional names for either HTTP/2 flaw.
Inventory the public edge as well as private NGINX listeners that accept untrusted clients. A vulnerability intelligence platform can help prioritize reachable deployments, while the owner confirms the running build and HTTP/2 setting. Record whether a proxy backend is used and whether connection pressure can occur; those facts distinguish the 123633 path.
How Should Teams Patch and Verify Production?
Patch externally reachable HTTP/2 deployments first, then cover internal services that accept less trusted traffic. The patch management record should include the product family, installed build, planned fixed build, and restart owner. A successful package installation alone does not prove that old NGINX workers have exited.
- Identify HTTP/2 listenersRecord the upstream or package build and whether requests proxy to a backend.
- Select the complete fixUse OSS 1.30.7 or 1.31.9, or the applicable Plus build covering both CVEs.
- Deploy and reloadTest service compatibility, apply the update, and confirm old workers have exited.
- Verify the running versionCompare the active binary and package information with the branch’s fixed release.
- Review operational evidenceExamine unexpected worker crashes and commands launched by NGINX as general warning signs.
Wiz advises temporarily disabling HTTP/2 if upgrading cannot happen immediately. On NGINX 1.25.1 or later, it describes using http2 off; in affected server blocks and removing the HTTP/2 parameter from listen directives. Test client compatibility, reload the service, and confirm the old workers exit. Re-enable HTTP/2 only after the fixed build is running.
Unexpected worker crashes or commands launched by NGINX merit investigation, according to Wiz, but they are general warning signs. Wiz also points to unusually long HTTP/2 connections carrying large amounts of data as a possible clue for 123007. Correlate those observations with local logs and change records before assigning a cause. Use vulnerability prioritization to keep the investigation tied to actual exposure.
What Do the Available Research Mentions Mean?
For August 20 through November 18, 2026, Brandefense Blackhole counted two matching dark-chat posts for CVE-2026-123007 and one for CVE-2026-123633. These are separate per-CVE post counts and may overlap. One public GitHub repository name matched CVE-2026-123007 in the November 18 source-pack query; its contents were not assessed.
- Brandefense Blackhole, CVE-2026-123007Yes2 matching dark-chat posts, Aug 20 to Nov 182026-11-18
- Brandefense Blackhole, CVE-2026-123633Yes1 matching dark-chat post, Aug 20 to Nov 182026-11-18
- GitHub name match, CVE-2026-123007Yes1 public repository, contents not assessed2026-11-18
Posts and repository names are research signals, not verified incidents or proof of active exploitation. The November 17 CISA KEV catalog snapshot in the source pack does not list either CVE, but catalog status is a dated fact. The patch decision follows the vendor’s affected versions, the reachable HTTP/2 configuration, and the server’s role.
Frequently Asked Questions
Does CVE-2026-123633 affect a static-only NGINX server?
F5 describes this flaw when HTTP/2 requests are proxied to a backend and the worker runs low on connection slots. That proxy condition does not describe a static-only server.
Which NGINX Plus build covers both HTTP/2 CVEs?
For the 37.0 path, F5 lists 37.0.8.1 for the later fix. For the 37.1 path, it lists 37.3.0.1. Confirm the active build after deployment.
Is disabling HTTP/2 a temporary option?
Wiz recommends temporarily disabling HTTP/2 if an immediate update is not possible. Test compatibility, reload NGINX, confirm old workers exit, and restore HTTP/2 after patching.
