Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/Two critical nginx http2 flaws what to patch first
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

Two Critical NGINX HTTP/2 Flaws: What to Patch First

Source: Check Point Blog•November 19, 2026 at 06:51 PM

Two Critical NGINX HTTP/2 Flaws: What to Patch First

The web server in front of your applications can now be taken over by someone with no login and no help from your own code. Two critical NGINX flaws, CVE-2026-123007 and CVE-2026-123633, make that possible when HTTP/2 is on. F5 and the NGINX project released fixes on November 18, 2026. Our…

The web server in front of your applications can now be taken over by someone with no login and no help from your own code. Two critical NGINX flaws, CVE-2026-123007 and CVE-2026-123633, make that possible when HTTP/2 is on. F5 and the NGINX project released fixes on November 18, 2026.

Our research team published a full advisory on the NGINX HTTP/2 flaws with version tables, mitigations, and hunting guidance.

Check Point WAF SaaS, Not Vulnerable – Our R&D team assessed these critical NGINX vulnerabilities and found that Check Point WAF as a Service (SaaS) is not vulnerable to them. The way the platform is built and configured doesn’t enable the conditions an attacker would need to exploit them. No customer action is required.

What the flaws do

HTTP/2 lets many requests, called streams, share one connection. NGINX tracks how much data it may send on that connection with a flow-control counter. CVE-2026-123007 breaks that accounting: a canceled stream’s refund pushes the counter past its limit, a later check wraps around, and an invalid length becomes an out-of-bounds memory copy.

The bug has been in NGINX since version 1.9.5, so it covers every release since HTTP/2 support arrived in 2015. Researchers ran code on a server that only served static files, with no backend application and no third-party modules.

CVE-2026-123633 is a use-after-free in connection handling. When NGINX acts as a reverse proxy and runs low on connection slots, it frees a busy connection mid-request and keeps using the memory. It affects NGINX from version 1.19.7.

How CVE-2026-123007 moves from an HTTP/2 session to code execution, with a summary of both flaws

F5 rates both flaws 9.2 on CVSS v4.0. Neither needs authentication. An attacker only has to open an HTTP/2 connection.

Why the front door is key

NGINX typically terminates HTTPS and routes requests to the applications and APIs behind it. One compromised server can expose the traffic, credentials, and secrets for every site it fronts. Failed attempts crash workers, which gives your team a signal to watch.

Researchers also chained a separate, unpatched Linux SCTP flaw to reach root and escape a container. Blocking the SCTP kernel module where you don’t need it closes that path until a kernel fix ships.

Where exploitation stands

A public proof-of-concept exploit exists for CVE-2026-123007, and national CERTs in Japan, Poland, and France issued alerts. As of November 18, 2026, there are no confirmed attacks in the wild, and neither CVE is in the CISA Known Exploited Vulnerabilities catalog.

The public exploit needs about 128 GB of HTTP/2 traffic on one connection and an AVX-512 processor, and it likely fails through a proxy. That slows mass attacks. Targeted attacks face a lower bar.

Three common controls will not carry you here. Researchers defeated ASLR by leaking memory first, WAF rules don’t inspect the HTTP/2 control frames involved, and access logs don’t record them.

Key numbers from the advisory, as of November 18, 2026.

Find your NGINX first

A server is exposed when three things are true: it runs an affected version, it accepts HTTP/2, and an attacker can reach it. Affected versions are NGINX Open Source 1.9.5 to 1.30.6 and 1.31.0 to 1.31.8, plus NGINX Plus 37.x before the fixed builds and NGINX Plus R34 to R36, which get no fix.

Check the version and configuration on the server, then confirm from outside whether it offers HTTP/2. If the second command prints ALPN protocol: h2, HTTP/2 is on.

Don’t close a finding on the version string alone. Linux distributions often backport fixes without changing the version number, and Ubuntu and Red Hat fixes were still pending on November 18. NGINX inside appliances, ingress controllers, and container images isn’t fixed by operating system updates. The retired Kubernetes ingress-nginx project won’t ship a fix for CVE-2026-123633, so plan a move to a maintained controller.

Where NGINX runs beyond a dedicated web server, and what to do in each case

What to do now

  • Inventory every NGINX instance, including container images, ingress controllers, load balancers, appliances, and origin servers behind your CDN.
  • Run the external HTTP/2 check on each internet-facing host and put servers that offer HTTP/2 at the top of the list.
  • Upgrade internet-facing servers to NGINX 1.30.7 or 1.31.9, or NGINX Plus 37.0.8.1 or 37.3.0.1.
  • Turn off HTTP/2 on listeners that must wait for a fix. gRPC needs HTTP/2 and breaks without it, so patch those services instead.
  • Restart NGINX after upgrading, because a reload keeps the old binary. Rebuild container images, then rerun the checks to confirm.

Then hunt for signs of earlier attempts: repeated worker crashes in the error log, NGINX workers starting shells or opening new outbound connections, unusually large and long-lived HTTP/2 sessions, and floods of WINDOW_UPDATE or RST_STREAM frames. None of these proves a compromise, and their absence doesn’t prove a server is safe.

The same release fixes three more critical flaws in the DNS resolver, HTTP/3, and the mail proxy. Turning off HTTP/2 doesn’t block them, so upgrading is the complete fix. Internal servers count too, since an attacker with a foothold in your network can use these flaws to move laterally.

What this means for Check Point WAF customers

Check Point R&D has assessed all five critical NGINX vulnerabilities disclosed in November 2026: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425.

WAF SaaS and WAF Agent Docker deployments (standalone)

Check Point WAF SaaS is not vulnerable to these five vulnerabilities, and neither are Check Point WAF Agent Docker images deployed with Check Point’s default configurations. In both cases, the configuration doesn’t enable the conditions required for exploitation:

  • HTTP/2 flaws (CVE-2026-123007, CVE-2026-123633): HTTP/2 is disabled on the WAF application listeners.
  • Resolver flaw (CVE-2026-123634): The standard WAF SaaS configuration and the default WAF Agent configuration don’t enable SSI or mirror subrequests.
  • HTTP/3 flaw (CVE-2026-121810): HTTP/3 and QUIC aren’t enabled.
  • Mail proxy flaw (CVE-2026-113425): Neither WAF SaaS nor WAF Agent uses NGINX mail proxy functionality.

WAF SaaS customers aren’t exposed to these five vulnerabilities through the assessed deployment configuration, and no customer action is required.

WAF Agent virtual machine deployments (IaaS)

For WAF Agent deployments that use Check Point-provided VM images, the assessment looks at the deployment architecture and the components handling incoming traffic:

  • Behind a cloud-managed load balancer (default and recommended): Check Point recommends deploying WAF Agent VMs behind cloud-managed Application Load Balancers (ALBs). Follow your cloud provider’s security advisories and remediation guidance for the managed load balancer infrastructure.
  • Without a load balancer: Check Point WAF Agent blocks all currently observed exploitation attempts associated with these five vulnerabilities, including where the VM is directly exposed. Check Point still recommends upgrading to the latest WAF Agent version available in the Check Point Portal, which incorporates the official NGINX security fixes.
  • Behind a customer-managed NGINX front end: If you run a separate NGINX reverse proxy in front of your WAF VMs, assess its version and configuration against the published CVEs and apply the relevant security updates where required.

Updated WAF Agent images for Docker and VM deployments

As an additional security measure, Check Point is preparing updated WAF Agent Docker and VM images based on NGINX version 1.30.7, with the latest official security fixes. Once the updated images are released:

  • Automatic upgrade enabled: You’ll receive the NGINX security update through the automatic upgrade process, with no manual intervention.
  • Automatic upgrade disabled: You must upgrade to the latest Check Point WAF Agent version as soon as it’s available.

Check Point strongly recommends keeping automatic upgrades enabled, so security fixes and product updates are deployed on time. You can upgrade your WAF Agent to the latest available version through the Check Point Portal. For details, see the WAF Agent upgrade instructions.

Check Point continues to monitor emerging security vulnerabilities and validate its protection capabilities to maintain the security and resilience of its WAF SaaS platform.

Closing the gap between advisory and action

An advisory gives you a list of affected versions. Your team still has to find where those versions run, which ones an attacker can reach, and which to fix first. That work takes time when NGINX sits in appliances, containers, and servers that nobody has looked at in years.

Exposure management shortens that path. Check Point Exposure Management brings together asset discovery, attack surface management, threat intelligence, prioritization, validation, and remediation guidance in one workflow. It shows where affected software runs across your internet-facing and internal assets, including servers outside your inventory.

Threat intelligence adds context on whether exploit code is public or attacks are underway, so you can rank a flaw like this against everything else on your list. Validation confirms whether an exposure is exploitable in your environment. Remediation guidance then helps your team fix issues in order of risk, with 160+ integrations and a 20-minute agentless setup.

← All articles

What this article says

More in Cybersecurity

All →
OAuth comes to the SonarQube Cloud-hosted MCP server
SonarSource

OAuth comes to the SonarQube Cloud-hosted MCP server

Automatic analysis for Bitbucket Cloud is now available
SonarSource

Automatic analysis for Bitbucket Cloud is now available

Identity context is essential for exposure management: Tenable One adds ways to bring in identity security data
Tenable

Identity context is essential for exposure management: Tenable One adds ways to bring in identity security data

Delphi language support is now built into SonarQube
SonarSource

Delphi language support is now built into SonarQube

Make no mistakes: Blameless postmortems in an age of agents
HackerOne

Make no mistakes: Blameless postmortems in an age of agents

Spying on Governments with Zero Lines of Malware: A Custom SoftEther Bridge in Webworm’s Toolkit
Rapid7

Spying on Governments with Zero Lines of Malware: A Custom SoftEther Bridge in Webworm’s Toolkit

More from Check Point

The Kill Switch is the Last Resort. Agentic Steering Is the First Move.
Check Point

The Kill Switch is the Last Resort. Agentic Steering Is the First Move.

Cyber or Not, the Lesson Is the Same: What a Week of Global Outages Teaches Us About Security Posture
Check Point

Cyber or Not, the Lesson Is the Same: What a Week of Global Outages Teaches Us About Security Posture

During the Microsoft 365 Disruption, Not A Single Email Was Lost
Check Point

During the Microsoft 365 Disruption, Not A Single Email Was Lost

Black Friday Cyber Crime 2026: Attacks on Retailers Surge 28% as Risky Domains Multiply
Check Point

Black Friday Cyber Crime 2026: Attacks on Retailers Surge 28% as Risky Domains Multiply

The Vulnerability Management Lifecycle: What Happens After Discovery?
Check Point

The Vulnerability Management Lifecycle: What Happens After Discovery?

Check Point Extends Its Penetration Testing Capabilities
Check Point

Check Point Extends Its Penetration Testing Capabilities