Skip to content
NGINX Vulnerabilities Allow Remote Code Execution

NGINX Vulnerabilities Allow Remote Code Execution

First seen 19 Nov 2026, 00:18 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 19, 2026 at 11:18 UTC

On November 18, 2026, F5 disclosed five vulnerabilities in NGINX, collectively termed NGINX2Root, affecting versions 1.9.5 to 1.31.8. The most severe, CVE-2026-123007, is an integer underflow in HTTP/2 flow control that allows unauthenticated remote code execution. CVE-2026-123633, an use-after-free vulnerability, requires HTTP/2 to be enabled and a reverse proxy configuration. Both vulnerabilities have a CVSS score of 9.2. Researchers confirmed successful exploitation in controlled environments, with proof-of-concept code publicly available. As of the latest reports, no active exploitation in the wild has been confirmed. Organizations using NGINX are urged to upgrade to versions 1.30.7 or 1.31.9 immediately or disable HTTP/2 as a temporary measure.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-11-18
F5 discloses NGINX vulnerabilities
F5 released security updates for five critical vulnerabilities in NGINX, including CVE-2026-123007 and CVE-2026-123633.
Shattered
2026-11-18
Patches released for NGINX
NGINX versions 1.30.7 and 1.31.9 were released to address the vulnerabilities, with recommendations to upgrade immediately.
Safe.Security
2026-11-18
CVE-2026-123007 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-11-18
CVE-2026-123633 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE

More articles in this cluster (58)

Following this threat?

Track F5 and CVE-2026-113425 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions of NGINX are affected?
NGINX versions from 1.9.5 to 1.31.8 are affected if HTTP/2 is enabled.
What should I do if I can't patch immediately?
If immediate patching is not possible, disable HTTP/2 in your NGINX configuration.
Is there evidence of exploitation in the wild?
As of now, there have been no confirmed reports of exploitation in the wild.