Tools & releasesImpact: High
Oleksandr Kuzmenko, EditorPublished 6 min readAI-assisted · editor-reviewed
TL;DR
- CVE-2026-123633 (use-after-free) and CVE-2026-123007 (integer underflow) both allow unauthenticated remote code execution.
- One vulnerability had lingered in the codebase for nearly six years, while the other had remained hidden for over a decade.
- Both vulnerabilities require HTTP/2 to be enabled; disabling HTTP/2 provides immediate mitigation if patches cannot be applied.
Key facts
- CVSS 4.0 Score
- 9.2 Critical
- Vulnerability IDs
- CVE-2026-123633, CVE-2026-123007
- Affected Web Servers Worldwide
- > 225 million websites
- Oldest Codebase Exposure
- NGINX 1.9.5 (released 2015)
- Coordinated Disclosure Date
- November 18, 2026
Source: Key facts — CVSS 4.0 Score
Source: Key facts. CVSS 4.0 Score: 9.2 Critical. Each figure is copied from the story.
- CVSS 4.0 Score9.2 Critical
Longstanding Memory Flaws Disclosed. Wiz Research, alongside Ikotas Labs, Metnir, Rapid7, and Xint, independently uncovered two critical remote code execution flaws in NGINX. Assigned CVE-2026-123633 and CVE-2026-123007, both carry a CVSS score of 9.2. One flaw had been present in the codebase for nearly six years, while the other had remained hidden for more than a decade since NGINX 1.9.5 in 2015. Wiz utilized its Wiz Atlas code scanning solution and frontier models Gemini 4 Carbon and ChatGPT 5.6 Sol to confirm that unauthenticated attackers could achieve code execution on default 64-bit deployments.
Attack Vectors and Affected Configurations. Both vulnerabilities strictly require HTTP/2 to be enabled. CVE-2026-123633 triggers a connection use-after-free under reverse-proxy workloads when available connection slots run low. CVE-2026-123007 triggers an invalid memory copy via integer underflow in flow control, enabling code execution even on static web servers over HTTPS. Standard ASLR protections fail to block the attack because both flaws permit preliminary memory read access.
Remediation and Workarounds. F5 and the NGINX project coordinated disclosure on November 18, 2026, releasing upstream patches. Teams unable to immediately deploy patched packages should mitigate immediately by removing http2 directives from their server configuration blocks and reloading the daemon.
When to use
- Apply immediately across all production web servers, ingress controllers, and reverse proxies running NGINX.
When NOT to use
- Do not leave HTTP/2 enabled on unpatched, internet-facing NGINX servers.
What to do today
- Update all NGINX deployments to the patched November 18, 2026 release.
- Temporarily disable HTTP/2 in server configuration blocks if immediate patching is not feasible.
Step names are taken from What to do today.
Step names are taken from What to do today. Update all NGINX deployments to the patched November 18, 2026 release.. Temporarily disable HTTP/2 in server configuration blocks if immediate patching is not feasible.
- Update all NGINX deployments to the patched November 18, 2026 release.
- Temporarily disable HTTP/2 in server configuration blocks if immediate patching is not feasible.
#NGINX#Wiz Atlas#Gemini 4 Carbon#ChatGPT 5.6 Sol
