Critical NGINX flaws can let attackers run code on web servers
F5 has patched five remote code execution bugs. Wiz says AI tools helped it find the two HTTP/2 bugs; no attacks in the wild have been reported.
Key takeaways
- F5 has patched five NGINX flaws that can let unauthenticated attackers run code on affected servers.
- The two most serious, called nginx2root, involve HTTP/2 and were found independently by five research teams.
- CERT-EU says no exploitation in the wild has been reported and urges quick updates.
- Censys counted about 8.8 million potentially exposed services, but researcher Florian Roth calls version-based exposure counts misleading.
- Disabling HTTP/2 mitigates the two HTTP/2 flaws while servers are being updated.
F5 has fixed five vulnerabilities in NGINX, the widely used web server, that can let an unauthenticated attacker run code with the privileges of an NGINX worker process, according to an advisory from CERT-EU, the cybersecurity service for EU institutions. F5 published its fixes on Wednesday. CERT-EU says no exploitation in the wild has been reported, but it recommends updating quickly, starting with servers exposed to the internet.
The two flaws drawing the most attention, dubbed "nginx2root" by researchers, affect how NGINX handles HTTP/2 traffic, BleepingComputer reports. Researchers at Wiz, Xint, Ikotas Labs, Metnir and Rapid7 found them independently. Wiz says NGINX powers more than 225 million websites.
What are the two main flaws?
The first, CVE-2026-123007, is a flow-control bug that can corrupt memory and affects versions back to one released in 2015, according to BleepingComputer and Wiz. Wiz says it showed code execution on a server delivering ordinary static files over HTTP/2, with no backend application. Xint also showed it could combine the flaw with a separate Linux kernel bug to break out of an NGINX Docker container and gain root access to the host, BleepingComputer reports.
The second, CVE-2026-123633, is a use-after-free bug that matters when NGINX accepts HTTP/2 connections and forwards requests to a backend server, BleepingComputer says. Wiz also demonstrated code execution with this flaw but is not releasing its exploit code for now.
Severity scores differ: CERT-EU lists each of the five flaws at 8.1, while Wiz's table rates all five 9.2 under CVSS 4.0. The other three flaws involve HTTP/3 proxying, DNS resolution and the mail proxy, and need specific configurations, CERT-EU says.
How widespread is the risk?
Accounts differ on how many servers are truly exposed. Judging by version numbers and HTTP/2 support, roughly 8.8 million NGINX services could be open to CVE-2026-123007, Censys estimated on Thursday, BleepingComputer reports. Censys says more than 511,000 services that had been exposed are now patched or mitigated.
Security researcher Florian Roth said the flaws are worse than Node2Shell and Java2Shell but are unlikely to pose an immediate danger to most NGINX servers, BleepingComputer reports. He said they are exploitable in non-default setups and called exposure claims based on version numbers alone misleading. Wiz, by contrast, says CVE-2026-123007 is exploitable in default configurations once HTTP/2 is enabled, and CERT-EU lists HTTP/2 on a listening port as its only precondition. An attacker can only use the two HTTP/2 flaws against a server that is unpatched, has HTTP/2 switched on and can be reached.
What should administrators do?
CERT-EU and BleepingComputer advise upgrading to the latest NGINX release; the fixes are in NGINX Open Source v1.30.7 stable and v1.31.9 mainline, BleepingComputer reports. Where upgrading is not yet possible, turning off HTTP/2 on exposed listeners mitigates the two HTTP/2 flaws, though not the other three, CERT-EU says.
What role did AI play?
Wiz says it found both HTTP/2 bugs using its AI-driven code scanning tool and used AI models from Google and OpenAI to confirm their impact. The company argues that AI is removing the complexity that once kept memory-safety flaws like these hidden, and that both defenders and attackers can now find long-standing bugs faster.
Questions readers are asking
Are the NGINX flaws being exploited?
CERT-EU says no exploitation in the wild has been reported, though researchers have shown working attacks in testing.
How can administrators protect their servers?
Upgrade to the latest NGINX release. If that is not possible right away, disabling HTTP/2 on exposed listeners mitigates the two HTTP/2 flaws, CERT-EU says.
Is every NGINX server at risk?
Not necessarily. The HTTP/2 flaws need HTTP/2 enabled on a reachable server, and the others need specific configurations. Florian Roth calls version-based exposure counts misleading, while Wiz says one flaw works in default setups with HTTP/2 on.
Sources
- #nginx
- #vulnerabilities
- #f5
- #http2
- #patching
Get the day's top AI & tech stories on WhatsApp: Follow the NextFish channel
Get stories like this every morning.
Related
Cybersecurity2 min
European Commission confirms it was hit by an AI-driven cyber campaign
Pay, leave and medical reimbursement tools were taken offline. The Commission says it has found no evidence of a data breach affecting staff as a whole.
Cybersecurity2 min
Ukraine and FBI arrest four suspects in alleged $40.5M ransomware ring
Prosecutors say the group posed as IT support, using AI-generated voice calls to trick staff into handing over access. At least 28 companies paid ransoms, they say.
Cybersecurity2 min
Palo Alto Networks to buy AI startup Applied Compute for $4.5 billion
The cybersecurity company is betting that businesses will run their own open-weight AI models and need them secured. Its CEO says the bet could outgrow its security business.
Cybersecurity3 min
Hijacked Microsoft Agent Framework package on PyPI hid a credential stealer
Two malware-laced releases of a Microsoft AI developer package were live on PyPI for under an hour. Researchers say anyone who installed them should rotate every exposed secret.