CISOOnline

AI unearths ‘internet breaker’ flaws in Nginx web server

Metnir ran its exploit for CVE-2026-123633 with ASLR enabled, taking about 10 minutes, nearly all of it spent on defeating memory layout randomization, and reproduced the use-after-free in OpenResty, crashing the shipped binaries of Kong, Apache APISIX, NGINX Gateway Fabric, and community ingress-nginx, all of which enable HTTP/2 by default.

Rapid7’s Fewer calculated that running his exploit requires transmitting roughly 128GB of HTTP/2 data to the target. That takes about two minutes on a 10Gbit/s network and 17 minutes on 1Gbit/s. The technique also relies on a memory-copy routine in glibc that is used only on CPUs with AVX-512 extensions, but these are common on servers.

“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 CDN terminating HTTP/2,” Yordan Ganchev, principal threat intelligence specialist at watchTowr, told CSO. “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.”

Patch and check what you’re actually running

Nginx Plus users should also update to 37.3.0.1 on the newer release line or 37.0.8.1 on the 37.0 line. The older R33 through R36 release line will never receive a fix because those versions have reached the end of technical support.



Source link