NGINX2Root (CVE-2026-123007): Find and fix NGINX security vulnerabilities
This text was generated using artificial intelligence (AI).As of November 19, 2026 – Updates have been available since November 18, a proof of concept is public. No attacks have been reported so far. Anyone operating NGINX with HTTP/2 on the internet should update promptly.
NGINX2Root is the collective name for five vulnerabilities in NGINX Open Source and NGINX Plus, which F5 closed on November 18, 2026, outside the regular patch cycle: CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425 and CVE-2026-123634. All five are memory errors in the worker processes of NGINX. Malformed requests without authentication can cause a worker to crash and corrupt memory. If ASLR is disabled or the attacker can circumvent it, executing malicious code is also possible.
CVE-2026-123007 and CVE-2026-123633 were discovered by Wiz Research. CVE-2026-123007 has been in the code since version 1.9.5 from 2015, affecting nearly every NGINX installation with HTTP/2.
NGINX Open Source, HTTP/2 as a Reverse Proxy (CVE-2026-123633)
1.19.7 to 1.31.8
1.30.7, 1.31.9
NGINX Open Source, HTTP/3 (CVE-2026-121810)
1.25.0 to 1.31.8
1.30.7, 1.31.9
NGINX Open Source, Mail Proxy (CVE-2026-113425)
0.5.33 to 1.31.8
1.30.7, 1.31.9
NGINX Open Source, Resolver with SSI/mirror (CVE-2026-123634)
0.6.18 to 1.31.8
1.30.7, 1.31.9
NGINX Plus (all five CVEs)
R33 to R36, 37.x before the fix versions
37.0.8.1, 37.3.0.1
Severity: CVSS 4.0: 9.2 (critical), CVSS 3.1: 8.1 (high) – for all five CVEs
Status: Proof of Concept for CVE-2026-123007 public, no attacks reported (as of November 19, 2026)
Patch available since: November 18, 2026
Overview
Five memory vulnerabilities in NGINX, exploitable without authentication and without user interaction.
Most affected is HTTP/2: CVE-2026-123007 goes back to version 1.9.5.
Fixed in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). Version 1.31.8 from October is still vulnerable.
After the update, restart NGINX. A reload does not load the new program.
Temporarily, disabling HTTP/2 helps against the two HTTP/2 vulnerabilities, not against the other three.
Which configurations are affected?
Whether a system is vulnerable depends on the enabled NGINX features:
CVE-2026-123007: HTTP/2 is active on a port. A flaw in flow control leads to an integer overflow and heap buffer overflow. This is the most common scenario.
CVE-2026-123633: NGINX accepts HTTP/2 connections and forwards requests to a backend. The use-after-free occurs when the worker runs out of worker_connections .
CVE-2026-121810: HTTP/3 (QUIC) is active and requests go to a backend.
CVE-2026-113425: NGINX runs as a mail proxy with auth_http. The error occurs when the client closes the connection during the authentication query.
CVE-2026-123634: One resolver is set, the target server name in proxy_pass includes variables and an SSI or mirrorsub-request resolves the same name.
The NGINX project itself classifies CVE-2026-123007 and CVE-2026-113425 as „major“, and the other three as „medium“. The CVE entries from F5 rate all five with CVSS 4.0 9.2.
With the same update, NGINX closes five more vulnerabilities, including an endless loop when reading request bodies over TLS 1.3 (CVE-2026-118899) and a buffer overflow at alias with try_files (CVE-2026-125283). They do not belong to NGINX2Root, but are another reason for the update.
Updates and transitional solutions
Update: NGINX Open Source to 1.30.7 or 1.31.9, NGINX Plus to 37.0.8.1 or 37.3.0.1. For CVE-2026-123633 alone, NGINX Plus versions 37.0.7.1 and 37.2.0.1 would suffice, the other four CVEs only close with the higher versions. F5 does not evaluate versions without manufacturer support; there are no fixes for them.
Restart instead of reload: One nginx -s reload only starts new workers from the already loaded program. Only a restart of the service (or a binary upgrade) brings the corrected code into memory.
Distributions: Debian, Ubuntu, Red Hat, and others often deliver NGINX with their own version number and backported corrections. There, the security update of the distribution counts, not the upstream version number. The same applies to container images and ingress controllers that come with NGINX.
If the update has to wait:
disable HTTP/2 (http2 from the listsremove from -directive or http2 off;) protects against CVE-2026-123007 and CVE-2026-123633.
Turning off HTTP/3 removes the basis for CVE-2026-121810.
Only allow Mail Proxy Listener for trusted networks (CVE-2026-113425).
SSI and mirror avoid or set server names in proxy_pass without variables (CVE-2026-123634).
Keep ASLR enabled on all NGINX systems. Without ASLR, a crash can more easily lead to code execution.
These measures do not replace the update.
Exploit Situation
A proof of concept for CVE-2026-123007 has been publicly available since November 18. No attacks on real systems have been reported until November 19. CERT-EU recommends checking the error logs for entries relating to worker processes that were terminated with a signal („exited on signal“). Frequent crashes of this sort may indicate attempted attacks.
NGINX is one of the most used web servers and reverse proxies in the DACH region. For entities under NIS-2, promptly closing known vulnerabilities is one of the required risk measures (Article 21 (2)(e) NIS-2 Directive). If an exploited gap leads to a violation of the protection of personal data, the 72-hour notification deadline applies under Article 33 GDPR.
Am I affected?
This affects any NGINX instance in the mentioned versions where the respective functionality is active. For CVE-2026-123007, HTTP/2 is sufficient, which is enabled on most publicly accessible web servers. Check:
What version is running? (nginx -v or package version of the distribution)
Is HTTP/2 or HTTP/3 active in a lists-directive?
Is NGINX running as a Mail Proxy or with resolver, SSI or mirror?
Are NGINX-based components in appliances, containers or Kubernetes ingress controllers?
Anyone who wants to know where NGINX is operating in their externally accessible infrastructure can use the CVE Quick Check Use at the end of this article. It shows exposed systems and the software recognizable from the outside.
Capture externally accessible NGINX services
NGINX often runs where no one looks anymore: as a reverse proxy in front of legacy applications, in test environments, or in service provider devices. LocateRisk detects NGINX on the externally visible systems of a company and makes forgotten instances visible. A Security Rating shows which services are accessible under your own domains.
The version number is not always disclosed by NGINX, and the affected functions are only partially recognizable from the outside. Therefore, checking the version and configuration remains the responsibility of operations. Continuous monitoring ensures that newly emerging NGINX systems enter the patch process. LocateRisk is Made in Germany, is exclusively operated in German data centers, and does not process data through US providers.
NGINX2Root is the collective name for five memory issues in NGINX Open Source and NGINX Plus (CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425, CVE-2026-123634) that F5 closed on November 18, 2026. They can be triggered without authentication, cause worker processes to crash, and may lead to code execution if ASLR is missing or bypassed.
Depending on the CVE, NGINX Open Source from 0.5.33, 0.6.18, 1.9.5, 1.19.7 or 1.25.0 up to and including 1.31.8 is affected. This was fixed in 1.30.7 and 1.31.9. For NGINX Plus, versions R33 to R36 and the 37 versions prior to 37.0.8.1 or 37.3.0.1 are affected. For distribution packages, the security update of the distribution counts.
Disabling HTTP/2 protects against CVE-2026-123007 and CVE-2026-123633, disabling HTTP/3 protects against CVE-2026-121810. Limit mail proxy listeners to trusted networks and avoid SSI or mirror with variable server names covers the other two. ASLR should remain enabled. The update does not replace any of these measures.
Status: November 19, 2026. This contribution serves general informational purposes and is not legal, security, or action advice for individual cases. The security situation and patch availability may have changed since publication; the relevant linked manufacturer advisory is always decisive. Despite careful research, we assume no liability for the currentness, correctness, and completeness.
CVE Quick Check
In just a few minutes, check whether there are any indications of a current CVE on your externally visible attack surface.
Initial assessment in just a few minutes via email.
Learn more during a free consultation with a LocateRisk consultant.
You'll receive this by email
companyYour Company, LLC
Verified CVECVE-2026-123633
Passive Assessment
Information About the CVEfound or not found
Want to find out more, book a demo or simply exchange ideas? We look forward to hearing from you!
We use cookies to optimize our website and our service.
Functional
Always active
Technical storage or access is strictly necessary for the lawful purpose of enabling the use of a particular service expressly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a message over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that have not been requested by the subscriber or user.
Statistics
The technical storage or access, which is carried out exclusively for statistical purposes.Technical storage or access used solely for anonymous statistical purposes. Without a subpoena, the voluntary consent of your Internet service provider, or additional records from third parties, information stored or accessed for this purpose alone generally cannot be used to identify you.
Marketing
Technical storage or access is necessary to create user profiles, to send advertisements, or to track the user on a website or across multiple websites for similar marketing purposes.