NGINX remote code execution vulnerability exploited in wild
Critical vulnerabilities in NGINX allow remote code execution via crafted HTTP requests, with proof-of-concept exploit published and active exploitation reported.
Sourcecisecurity.org — open the original
What to check
- Applies to
- The 4 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
Multiple critical vulnerabilities have been discovered in NGINX web server software affecting versions from 0.6.27 through 1.30.0, as well as NGINX Plus and related F5 products. The most severe vulnerability, CVE-2026-42945, is a heap buffer overflow in the ngx_http_rewrite_module that allows remote code execution on systems without ASLR protection. An unauthenticated attacker can exploit these flaws by sending specially crafted HTTP requests to crash worker processes or, in the worst case, achieve remote code execution.
VulnCheck has reported that CVE-2026-42945 is being actively exploited in the wild, and DepthFirst has published a proof-of-concept exploit. The vulnerabilities span multiple NGINX components including the rewrite module, SCGI/uWSGI modules, SSL module, and charset module. Exploitation could allow attackers to install malware, exfiltrate data, or establish persistence on compromised systems depending on privilege levels.
Immediate patching is required for all affected NGINX deployments. Organizations should prioritize internet-facing NGINX instances and systems without ASLR enabled. The widespread deployment of NGINX across web infrastructure, reverse proxies, and load balancers makes this a critical threat to government, business, and enterprise environments globally.
Mentioned in this report
Source reporting: https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-nginx-could-allow-for-remote-code-execution_2026-051
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,433 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs