Blog

NGINX HTTP/2 Vulnerabilities (CVE-2026-123007, CVE-2026-123633): What to Know and What to Do First

Company & Product News
Zero-Days
NGINX HTTP/2: What We Know and What We Need

TL;DR

  • Two vulnerabilities in NGINX's HTTP/2 handling were disclosed and fixed on November 18, 2026.
  • Only servers with HTTP/2 enabled are exposed. Researchers demonstrated remote code execution in the lab. There are no reports of exploitation in the wild.
  • Fixed in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). NGINX Plus has its own fixed releases.
  • Where you can't upgrade yet, turning off HTTP/2 closes the known attack path. Check first for gRPC and other services that need HTTP/2.

What happened

On November 18, the NGINX project released fixes for two flaws in its HTTP/2 implementation, found independently by several research teams.

  • CVE-2026-123007 is an error in HTTP/2 flow control that can corrupt memory. It affects NGINX Open Source 1.9.5 through 1.31.8 and has been shown against servers that simply deliver static files over HTTPS.
  • CVE-2026-123633 is a use-after-free that can occur when NGINX runs low on connections while proxying HTTP/2 requests. It affects 1.19.7 through 1.31.8.

A related HTTP/3 flaw, CVE-2026-121810, was fixed in the same release.

How serious is it?

Researchers report achieving remote code execution against official NGINX builds in lab conditions and have not released their exploit code. There are no reports of exploitation in the wild. nginx.org rates the flaws "major" and "medium"; public coverage cites a CVSS 4.0 score of 9.2. Because NGINX is the front door for so many services, we recommend acting now.

Why patching is harder than it looks

  • It's the front door. Restarting the servers that carry every request needs a change window.
  • Patched packages aren't everywhere yet. At the time of writing, Debian and Ubuntu have not shipped fixed packages.
  • NGINX hides in many places: custom builds, NGINX Plus, and products that bundle their own copy.

What to do now

  1. Find every NGINX with HTTP/2 enabled. The version alone doesn't tell you whether a server is exposed.
  2. Upgrade internet-facing servers first to 1.30.7 or 1.31.9, or your vendor's fixed release.
  3. Where you can't upgrade yet, turn off HTTP/2 on affected servers, after checking for gRPC and other services that depend on it.
  4. Track every mitigated server until it's upgraded, then turn HTTP/2 back on.

What turning off HTTP/2 does

Browsers and standard clients fall back to HTTP/1.1 automatically, so typical websites keep working. Services that require HTTP/2, most notably gRPC, stop working through that server. Busy sites with many files may load somewhat more slowly.

How Remedio helps

Remedio finds every running NGINX on a host, including custom builds and NGINX Plus, and checks its live configuration and whether its distribution has shipped a fix. From the NGINX finding, customers can:

  • Mitigate: Remedio saves the current configuration, turns off HTTP/2 for every site on that NGINX, tests the new configuration, and applies it with a reload. If the test fails, the original configuration is restored and NGINX keeps running unchanged. The change can be undone with a click.
  • Plan the upgrade: create a list of affected servers to drive the move to fixed releases.

Mitigated servers are tracked separately from fully patched ones. This version covers NGINX running directly on servers. 

The mitigation reduces exposure. Upgrading remains necessary for complete remediation, and it also fixes several other NGINX issues released at the same time. newly disclosed critical flaw in the Java runtime (dubbed Java4Shell and identified by CVE-2026-114938, it) carries a 9.2 CVSS score and enables pre-authentication remote code execution across core enterprise tools like Jira, Keycloak, and Jenkins.


Want to learn more?See Remedio In Action.   Book a Demo

References

  1. CVE-2026-123007
  2. CVE-2026-123633
  3. NGINX Security Advisories

About Author

Matt Rowe

Matt Rowe

Chief Technology Officer

Remedio's CTO, Matt brings over 20 years of leadership building and scaling secure technology platforms for the likes of Amazon, Synchrony Financial, and GE. Matt is passionate about advancing scalable, outcome-driven cybersecurity for critical systems.

Fix Misconfigurations Without Fear

Automate configuration security while keeping full control.

Book a Demo