Powered by MOMENTUMMEDIA
For breaking news and daily updates, subscribe to our newsletter

2shell2much: NGINX2Root vulnerabilities potentially expose more than 10 million websites

Security researchers have uncovered critical vulnerabilities in NGINX, a web server used by more than 80 per cent of Fortune 500 companies.

• Thu, 19 Nov 2026 •
2shell2much: NGINX2Root vulnerabilities potentially expose more than 10 million websites

The vulnerability apocalypse is continuing apace, with another batch of newly disclosed vulnerabilities in the NGINX web server revealed overnight, and they are already causing more than a bit of concern among cyber security analysts and practitioners.

Dubbed NGINX2Root by researchers at Xint, which helped uncover the flaws, the motley crew consist of five distinct NGINX vulnerabilities and one Linux kernel vulnerability.

“Each has a proven exploit. The most severe enables unauthenticated remote code execution; chained with a separate Linux kernel vulnerability, it can lead to host root,” Xint said in a blog post.

 
 

“Specifically, the most severe vulnerability is in nginx HTTP/2 flow control. An unauthenticated remote attacker can corrupt memory in an nginx worker, leak memory addresses, and overwrite the pointer to a cleanup function that runs when a connection closes.

“This can be used to execute commands with worker privileges and receive the output over an existing connection.”

The five NGINX vulnerabilities are CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425. NGINX versions 1.9.5 to 1.31.8 are impacted, while a fix has been applied in version 1.31.9.

CVE-2026-123007 is of particular concern, according to Rapid7, which has already developed a proof-of-concept exploit.

“nginx can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can exploit this error by cancelling queued response data, then make nginx use an invalid length when copying a later response,” the company’s Stephen Frewer said in a technical analysis of the bug.

“The resulting memory corruption can disclose data, interrupt service, and execute code with the nginx worker process's permissions.”

According to WatchTowr’s principal threat intelligence specialist, Yordan Ganchev, even if an organisation does not make use of NGINX – it’s one of the internet’s most widely used reverse proxy and load-balancer services, after all – “some other service you rely on most likely does.”

“Two noteworthy bugs include CVE-2026-123633 and CVE-2026-123007, both of which require HTTP/2 to be explicitly enabled and used. Exploitation is by no means a walk in the park, as the vulnerable systems must be directly exposed to the internet with no WAF or a CDN terminating HTTP/2,” he said.

“Memory corruption can also be tricky, as an effective exploit must properly groom and shape the memory heap and handle different NGINX versions, builds, and configuration variants. And when the system is internet-facing and under load, exploitation can cause more crashes than successful code execution.

“The vulnerabilities are real, and our guidance remains the same. Prioritise internet-exposed, affected systems. For systems with HTTP/2 enabled, patch them and audit for signs of compromise.

“If patching is not immediately possible, consider temporarily disabling HTTP/2 traffic processing.”

Cyber DailyWant to see more stories from trusted news sources?
Make Cyber Daily a preferred news source on Google.
Tags: