
On 18 November 2026, F5 disclosed five critical vulnerabilities affecting NGINX web servers, collectively named NGINX2Root by security researchers at Xint.
The most significant vulnerability, CVE-2026-123007, allows unauthenticated attackers to potentially execute arbitrary code through specially crafted HTTP/2 traffic.
With NGINX widely deployed across enterprise applications, reverse proxies, APIs and cloud infrastructure, organisations should urgently assess affected systems.
NGINX2Root refers to five independent memory-corruption vulnerabilities affecting NGINX's HTTP/2, HTTP/3, DNS resolver and mail proxy components.
CVE-2026-123007 involves an integer underflow in HTTP/2 flow-control calculations. By manipulating connection settings and cancelling queued responses, attackers can trigger incorrect memory handling and heap corruption.
Successful exploitation may allow remote code execution (RCE) without authentication, initially with NGINX worker-process privileges.
Researchers also demonstrated chaining NGINX exploitation with a separate Linux kernel vulnerability to achieve root-level access, including container escape.
The following vulnerabilities affect NGINX Open Source installations, depending on their enabled modules and configuration.
Fixed versions: NGINX Open Source 1.30.7 or 1.31.9, or vendor-confirmed patched packages. Affected NGINX Plus installations require the relevant F5 security release.
Successful exploitation could expose organisations to:
Internet-facing NGINX instances represent particularly significant exposure because attackers may exploit vulnerable configurations without valid credentials.
Recommendations for IT and Security Teams
Organisations should immediately update affected NGINX installations to prevent potential remote code execution and infrastructure compromise.
Check the installed NGINX version:
nginx -v
Review enabled modules and configuration:
nginx -V
nginx -T
Assess internet-facing servers, reverse proxies, containers and Kubernetes ingress controllers.
The recommended remediation is to upgrade to an officially patched release:
For Linux installations, update using the configured vendor repository:
Ubuntu/Debian:
sudo apt update
sudo apt install --only-upgrade nginx
RHEL/Rocky Linux:
sudo dnf upgrade nginx
Ensure the repository actually provides a patched package. Distribution-maintained packages may contain backported fixes without changing to the upstream version number.
Disable HTTP/2 on affected NGINX listeners to mitigate CVE-2026-123007 and CVE-2026-123633.
For supported NGINX versions, configure:
server {
listen 443 ssl;
http2 off;
server_name example.com;
}
For older configurations, remove http2 from the listen directives.
Validate and reload the configuration:
sudo nginx -t
sudo systemctl reload nginx
Important: Disabling HTTP/2 does not remediate the remaining three NGINX2Root vulnerabilities. Apply the relevant vendor patches and review affected HTTP/3, DNS resolver and mail proxy functionality.
Confirm the patched version, restart NGINX to replace vulnerable worker processes, and validate that all applications remain operational.
nginx -v
sudo nginx -t
sudo systemctl restart nginx
NGINX2Root highlights the importance of continuous vulnerability management and penetration testing.
Blacklock combines automated vulnerability scanning, expert-led penetration testing and AI-assisted vulnerability validation to help organisations identify and remediate emerging threats.
Explore our recent security research:
Blacklock also provides free vulnerability detection tools:
Protect your infrastructure before attackers exploit emerging vulnerabilities.
Visit Blacklock Security to explore continuous vulnerability scanning and penetration testing services.
Join our newsletter today and enhance your knowledge with valuable insights. It's quick, easy, and free!
