NGINX Security Release: How To Fix for 10-Year-Old HTTP/2 Flaw

NGINX Security Release_ Fixing HTTP_2 Flaw
NGINX Security Release_ Fixing HTTP_2 Flaw

HOC Shorts |

F5 and the NGINX security release pushed on November 18, 2026, fixing five critical vulnerabilities (each rated 9.2 on CVSS v4.0) alongside five additional NGINX flaws.

  • The Headline Bug (`CVE-2026-123007`): A decade-old bug (affecting NGINX since version `1.9.5`) in how NGINX manages HTTP/2 traffic flow can let an unauthenticated attacker trigger memory corruption and run code on the server.
  • Patched Versions: Upgrade NGINX Open Source to `1.30.7` (stable) or `1.31.9` (mainline), and upgrade NGINX Plus to `37.0.8.1` or `37.3.0.1`.
  • Pro Tip: Simply reloading your NGINX config is not enough—you must restart the NGINX process so the newly patched binary actually runs in memory.

NGINX Security Release: Urgent Fixes for a 10-Year-Old HTTP/2 Flaw and Critical Bugs

If you run websites or apps behind NGINX, drop what you are doing and check your server versions today. F5 and the NGINX project rolled out an emergency security update fixing five high-severity flaws—each scoring 9.2 out of 10—led by a 10-year-old bug in NGINX’s HTTP/2 handling.

Security researchers across Rapid7, Wiz, Tenable, and Xint independently uncovered these issues, and proof-of-concept exploit code is already public. While there are no confirmed wide-scale attacks in the wild yet, public exploit code means automated scans usually follow fast.

What Went Wrong Under the Hood?

Modern web traffic relies heavily on HTTP/2 to load pages and APIs faster over a single connection. The headline bug, tracked as `CVE-2026-123007`, has been hiding in NGINX since version `1.9.5`.

Here is the plain-English version of how attackers can abuse it:

[Attacker Opens HTTP/2 Connection]
│
▼
[Cancels Queued Data & Sends Window Updates]
│
▼
[Flow-Control Math Underflows (CVE-2026-123007)]
│
▼
[Memory Corruption ──► Potential Code Execution on Worker]

  • Broken Flow-Control Math: HTTP/2 uses “flow-control credits” to stop a fast server from overwhelming a slower client. By cancelling queued response data and sending carefully timed `WINDOW_UPDATE` frames, an attacker can trick NGINX into miscalculating byte counts—causing an integer underflow.
  • Memory Corruption Risk: That math error can corrupt memory buffers and potentially let an unauthenticated attacker execute code using the NGINX worker process’s permissions.
  • Four Other 9.2-Rated Flaws: The update also tackles four other 9.2-rated bugs tied to specific setups—including high connection pressure during backend proxying (`CVE-2026-123633`), variable-based proxying with SSI or mirror subrequests (`CVE-2026-123634`), HTTP/3 (`CVE-2026-121810`), and mail proxy configurations (`CVE-2026-113425`), plus five additional security fixes.

Affected & Fixed Versions at a Glance

Software Branch Vulnerable Versions Fixed Version to Install
NGINX Open Source (Mainline) 1.31.0 to 1.31.8 1.31.9
NGINX Open Source (Stable) 1.9.5 to 1.30.6 1.30.7
NGINX Plus (37.0.x) 37.0.0 to 37.0.7.1 37.0.8.1
NGINX Plus (37.x) 37.1.0 to 37.2.0.1 37.3.0.1

How to Fix? Pro Tips for Admins & Server Owners

  • Pro Tip 1 — Restart, Don’t Just Reload: A standard `nginx -s reload` swaps configuration files without replacing the running binary in memory. Restart the NGINX service completely after upgrading so the patched code takes effect.
  • Pro Tip 2 — Check If HTTP/2 Is Actually Active: Run a quick OpenSSL check against your server to see if `h2` (HTTP/2) is negotiated:

openssl s_client -alpn h2 -connect yourdomain.com:443 < /dev/null 2>/dev/null | grep "ALPN protocol"

If your site sits behind a CDN, test your origin server directly as well.

  • Pro Tip 3 — Use Temporary Mitigations Only If Needed: If you cannot patch right away, turning off HTTP/2 helps block `CVE-2026-123007` and `CVE-2026-123633`, though it won’t stop the other flaws (like HTTP/3 or mail proxy bugs). Treat disabling features as a temporary bridge until you upgrade.
  • Pro Tip 4 — Harden Worker Privileges & Kernel Patches: Make sure NGINX workers run with minimal privileges rather than unnecessary root access, and keep your underlying Linux kernel updated against local privilege-escalation flaws.

Join Our Club

Enter your Email address to receive notifications | Join over Million Followers

Previous Article
Optimizely Breach_ OPTIMJACK

Optimizely Breach (OPTIMJACK): What Affected Web Owners

Next Article
PHP Security Fixes_ 7 Critical Flaws Patched

PHP Security Fixes: 7 Critical Flaws Patched Across All Versions

Related Posts