Vulnerabilities

F5 Patches NGINX Vulnerabilities: HTTP/2 Flaw Could Allow Remote Code Execution

F5 has fixed five NGINX vulnerabilities. CVE-2026-123007 can trigger a heap buffer overflow in HTTP/2 handling and, in some cases, allow code execution.

F5 Patches NGINX Vulnerabilities: HTTP/2 Flaw Could Allow Remote Code Execution

On November 18, F5 released fixes for five vulnerabilities in NGINX Open Source and NGINX Plus. CVE-2026-123007 is a flaw in HTTP/2 flow control that can lead to a heap buffer overflow. It can crash the NGINX process or corrupt memory. If ASLR is disabled or an attacker can get around it, the flaw can also allow remote code execution. CERT-EU reports that researchers have shown the vulnerability can be exploited, but no attacks using it have been seen so far.

What happened

CVE-2026-123007 is triggered when NGINX processes specially crafted traffic and the HTTP/2 flow-control window goes over its allowed limit. A server is only vulnerable if HTTP/2 is enabled on a listening port. F5 says the flaw can crash a worker process, corrupt memory and, under certain conditions, allow code execution.

CERT-EU lists five vulnerabilities covered in F5’s advisory. Which versions are affected depends on the product, the release branch and the specific vulnerability. Fixes for CVE-2026-123007 are available for NGINX Open Source and NGINX Plus. According to F5, the other products listed in its advisory are not affected by this flaw.

Who is affected and what to do

The issue matters most to administrators of web servers and reverse proxies, especially those that handle internet-facing traffic. Check standalone NGINX installations, and also look for NGINX in container images, virtual machines and services deployed by application teams.

  • Find out which NGINX version you run and check whether your configuration uses HTTP/2.
  • Upgrade NGINX Open Source to at least version 1.31.9 or 1.30.7, depending on your branch.
  • For NGINX Plus, apply version 37.3.0.1 or 37.0.8.1, based on your branch and F5’s guidance.
  • If the update requires a maintenance window, assess how exposed the service is and patch public-facing servers first.
  • After updating, check logs and monitoring alerts for unusual worker process crashes.

SecurHUB’s take

Organizations should regularly review how exposed their edge servers and proxies are, along with their patch management process. Security audits can help identify which instances are reachable from the internet and how quickly updates can be rolled out safely.

Sources: F5 – CVE-2026-123007, CERT-EU – NGINX vulnerabilities

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk