Skip to content
Québec’s technology magazineYouTube ↗
Québec TestTechnology, from here
Understand. Compare. Choose.
Search
Security and privacy

Two critical NGINX flaws expose HTTP/2 servers: urgent update required

Québec TestPublished · 2 min read
Two critical NGINX flaws expose HTTP/2 servers: urgent update required
Illustrative image

NGINX administrators should act quickly. Two critical flaws in HTTP/2 request processing may allow unauthenticated remote code execution. F5 released fixes on November 18, 2026, and government cybersecurity agencies are urging organizations to update immediately.

NGINX HTTP/2 network security illustration
The flaws affect NGINX HTTP/2 processing. Illustration: Québec Test.

At a glance

  • CVE-2026-123007 and CVE-2026-123633 are rated critical.
  • They can be exploited remotely without an account when HTTP/2 is exposed.
  • Fixed open-source releases include NGINX 1.30.7 and 1.31.9, along with corresponding NGINX Plus updates.
  • If patching is not immediately possible, temporarily disabling HTTP/2 reduces exposure.

Why these flaws matter

NGINX is widely deployed as a web server, reverse proxy and load balancer. The newly disclosed vulnerabilities affect how certain HTTP/2 requests are parsed. A remote attacker may be able to send specially crafted traffic that corrupts memory and potentially executes code on the server.

The unauthenticated attack path is the key concern: an attacker does not need prior access. Exposure still depends on configuration. Servers that do not offer HTTP/2 are not affected through this specific vector, while internet-facing services that do should be treated as high priority.

Which versions should be installed?

For NGINX Open Source, the corrected branches include versions 1.30.7 and 1.31.9. NGINX Plus customers should apply the release recommended by F5 for their branch. Linux administrators should also check their distribution advisory because vendors may backport the fix to a package whose version number appears older.

After updating, restart or reload NGINX and confirm the running version. Review containers, base images and disaster-recovery environments as well: an outdated image can reintroduce the vulnerability during a future deployment.

Recommended response

  1. Inventory exposed NGINX servers and identify those accepting HTTP/2.
  2. Install official fixes or vendor-supplied packages.
  3. Validate configuration and running versions after restart.
  4. Monitor logs for abnormal HTTP/2 traffic, crashes or unexpected restarts.
  5. If patching must be delayed, disable HTTP/2 temporarily and document the compensating control.

The public advisories describe the risk and available fixes; they are not proof that any particular organization has been compromised. Teams should avoid premature conclusions while still treating remediation as urgent.

Sources