NGINX HTTP/2 RCE vulnerabilities
This message is intended for U-M IT staff responsible for systems running NGINX.
Summary
Wiz reports two critical NGINX HTTP/2 vulnerabilities, CVE-2026-123633 and CVE-2026-123007, that can allow unauthenticated remote code execution. Identify affected deployments and update to a release that fixes both flaws. If an update cannot be applied immediately, temporarily disable HTTP/2 after testing compatibility.
The need for immediate action supersedes the remediation timeframes in Vulnerability Management (DS-21).
Problem
Two memory-safety flaws in NGINX HTTP/2 processing can compromise the server and the websites or APIs it serves. Both require HTTP/2 to be enabled.
- CVE-2026-123633 is an HTTP/2 connection use-after-free: connection memory can be freed while a request still uses it during reverse-proxy processing under connection-slot pressure.
- CVE-2026-123007 is an HTTP/2 send_window integer-underflow flaw. Incorrect flow-control accounting can lead to an out-of-bounds memory copy, memory disclosure, and heap corruption.
Threats
Both vulnerabilities are rated as Critical (CVSS 4.0: 9.2) and report successful laboratory proof-of-concept remote code execution. Successful exploitation could expose sensitive data, permit website tampering, or disrupt services. No active exploitation is known in the wild.
CDN/WAF protection depends on implementation and must not be assumed.
Affected Systems
- NGINX OSS:
- CVE-2026-123633 starts at 1.19.7
- CVE-2026-123007 starts at 1.9.5
- Reported fixed releases for both: 1.30.7 stable and 1.31.9 mainline.
- NGINX Plus:
- R33 and 37.0.0 are the first affected branches/versions.
- 37.0.7.1 and 37.2.0.1 are fixes for CVE-2026-123633
- 37.0.8.1 and 37.3.0.1 for CVE-2026-123007
Both flaws require HTTP/2. The use-after-free affects reverse-proxy processing when connection slots run low; the integer-underflow flaw can also affect static-file serving.
Web sites that are only accessible via Cloudflare are believed to be protected from direct exploitation; however, if the server’s firewall doesn't block non-Cloudflare traffic, systems are still vulnerable to exploitation.
Detection
Review deployment inventory, installed NGINX package versions, vendor patch status, and effective HTTP/2 configuration. Investigate unexpected NGINX worker crashes or commands launched by NGINX; these are general warning signs, not confirmed indicators of either vulnerability.
Unusual long-lived HTTP/2 connections with large traffic volumes may warrant investigation but are not conclusive evidence.
Action Items
Identify NGINX versions and HTTP/2-enabled configurations; prioritize deployments exposed to access from the internet.
Verify and apply a vendor-supported release or patch addressing both CVEs as soon as available.
If upgrading is not immediately possible, temporarily disable HTTP/2: on NGINX 1.25.1 or later. Set HTTP/2 off in affected server blocks, and remove the HTTP/2 parameter from listen directives where present. Test application compatibility, reload NGINX, and confirm old workers have exited. Re-enable HTTP/2 after upgrading.
How We Protect U-M
ITS provides CrowdStrike Falcon to units, which should be installed on all U-M owned systems (Windows, macOS, and Linux operating systems, whether workstations or servers). Falcon administrators in ITS and in U-M units use the Falcon console to investigate and remediate issues.
Information for Users
Not applicable to routine end-user device updates; the recommended actions are for administrators of affected NGINX deployments.
Questions, Concerns, Reports
Please contact ITS Information Assurance through the ITS Service Center.