AI & Tech

AI found more critical bugs in another widely used technology running 225M websites

These include critical remote code execution flaws that let attackers hijack NGINX servers with HTTP/2 enabled, as well as the millions of websites running NGINX, to steal sensitive data and disrupt services.

✦ Extractive summary — built from the sources' own reporting•From 1 source•2 min read•Updated November 18, 2026, 9:11 PM UTC
Key points
  • Hot on the heels of serious vulnerabilities in seemingly every other widely used software powering the entire internet, F5 today released emergency patches for 10 bugs in open source NGINX.
  • In CVE-2026-123007, incorrect flow-control accounting leads to an invalid memory copy.” Rapid7’s team also published a proof-of-concep t to demonstrate leveraging CVE-2026-123007 for unauthenticated remote code execution against a vulnerable linux/amd64 Docker image running nginx version 1.31.8.
  • The research team dubbed the six bugs “ nginx2root.” The AI-powered offensive security firm also published videos demonstrating attacks using CVE-2026-123007 to execute commands as the NGINX worker inside a container, and then using the kernel vulnerability to escalate to root on the host.

“We continue to monitor closely and will share updates via myF5 as we learn more.” As with all of the other recently disclosed vulnerabilities in foundational technologies like PHP, Apache, and Java, these critical NGINX bugs were uncovered by researchers using AI.

Additional details
  • Tomer Schwartz, Wiz’s chief technology officer of exposure management and AppSec, helped find the bug, along with researchers from Ikotas Labs, Metnir, Rapid7, and Xint working independently.
  • Xint found three other NGINX flaws, plus a separate vulnerability in the Linux kernel that can be chained with any of the five NGINX vulnerabilities to gain root privileges on the host.
  • These two, tracked as CVE-2026-123633 and CVE-2026-123007, both received a critical, 9.2 CVSS rating, and CVE-2026-123007 affects versions dating back to NGINX 1.9.5 in 2015.
  • “Both vulnerabilities are memory-safety issues in how NGINX handles HTTP/2 traffic,” Schwartz and fellow Wiz kid Nir Ohfeld said in a Wednesday blog about the two bugs.
  • All of the security shops listed earlier independently found at least one of these two CVEs - most, if not all, with an AI assist - and reported them to F5.

How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →

Advertisement

Every article behind this summary — 1 article from 1 outlet