NGINX2Root: Five nginx Flaws, Led by CVE-2026-123007. How to Find, Mitigate, and Patch Now
Five nginx flaws, led by CVE-2026-123007, allow memory corruption and RCE.
NGINX2Root is a set of five vulnerabilities in nginx, with CVE-2026-123007 being the most critical. This memory corruption bug in HTTP/2 handling can lead to worker process crashes and remote code execution with the privileges of the nginx worker. F5 rates the lead flaw at 9.2/10 for CVSS v4.0 and 8.1/10 for CVSS v3.1. Fixes are available in NGINX Open Source 1.30.7 and 1.31.9, and NGINX Plus, with disabling HTTP/2 serving as a temporary mitigation.
AI summary of the linked source. Not reviewed by an editor. How this works
Run F5?
Get an email when a new story names F5, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonFive vulnerabilities collectively dubbed NGINX2Root, led by CVE-2026-123007, expose nginx deployments to memory corruption in HTTP/2 handling, potentially allowing attackers to crash worker processes or execute arbitrary code with worker-level privileges. Because nginx is one of the most widely deployed web servers globally, the blast radius of an unpatched deployment is enormous, particularly for internet-facing infrastructure. F5's high CVSS scores (9.2 on v4.0) reflect that exploitation requires no authentication and can be triggered remotely. Organizations without a disciplined patch cycle or asset inventory risk remaining exposed long after fixes are available, turning a known vulnerability into an active breach opportunity.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Endpoint detection and response (EDR and XDR)
Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- cve: CVE-2026-123633
- cve: CVE-2026-123007
- cve: CVE-2026-123634