{"id":10460,"date":"2026-11-18T23:36:40","date_gmt":"2026-11-18T23:36:40","guid":{"rendered":"https:\/\/cybersecurityinfocus.com\/?p=10460"},"modified":"2026-11-18T23:36:40","modified_gmt":"2026-11-18T23:36:40","slug":"ai-unearths-internet-breaker-flaws-in-nginx-web-server","status":"publish","type":"post","link":"https:\/\/cybersecurityinfocus.com\/?p=10460","title":{"rendered":"AI unearths \u2018internet breaker\u2019 flaws in Nginx web server"},"content":{"rendered":"<div>\n<div class=\"grid grid--cols-10@md grid--cols-8@lg article-column \">\n<div class=\"col-12 col-10@md col-6@lg col-start-3@lg\">\n<div class=\"article-column__content\">\n<div class=\"container\"><\/div>\n<p class=\"wp-block-paragraph\">Nginx, the web server estimated to power a third of the internet, has shipped fixes for multiple vulnerabilities, including a critical unauthenticated remote code execution flaw that puts millions of websites at risk and has existed in the code for over a decade. Researchers from several security firms independently found some of the same flaws by using AI agents, adding to a string of recent AI-discovered vulnerabilities in widely used internet technologies such as PHP, Node, OpenSSH, and Java.<\/p>\n<p class=\"wp-block-paragraph\">The most severe flaw, tracked as CVE-2026-123007, lets an attacker manipulate flow-control windows in the HTTP\/2 protocol implementation to trigger an out-of-bounds memory copy that researchers from Xint.io <a href=\"https:\/\/xint.io\/blog\/nginx2root-remote-code-execution\">turned into command execution with Nginx worker privileges<\/a>. The vulnerability affects every official Nginx release for more than 10 years since version 1.9.5, which originally added HTTP\/2 support in 2015.<\/p>\n<p class=\"wp-block-paragraph\">A second HTTP\/2 flaw, CVE-2026-123633, is a use-after-free vulnerability affecting releases 1.19.7 through 1.31.8. Both are fixed in Nginx 1.31.9 and 1.30.7, which <a href=\"https:\/\/nginx.org\/en\/security_advisories.html\">F5 released<\/a> along with fixes for eight other vulnerabilities.<\/p>\n<p class=\"wp-block-paragraph\">Xint\u2019s researchers, who used the company\u2019s own autonomous AI harness, found five of the flaws and discovered a separate Linux kernel vulnerability in the SCTP subsystem that can be chained with any of those flaws to gain root privileges on the server. The company has dubbed the collection <a href=\"https:\/\/nginx2root.com\/\">nginx2root<\/a>.<\/p>\n<p class=\"wp-block-paragraph\">In their tests the exploit chain escaped a Docker container running Nginx and obtained root on the underlying host. The kernel flaw has existed since Linux 4.15, released in 2018, and has no CVE or patch so the company is withholding details until distributions can ship a fix.<\/p>\n<p class=\"wp-block-paragraph\">The exposure of web servers on the internet is vast with the Shodan search engine showing 56.7 million hosts running Nginx, and 98.9% of those that disclose their version report one in the vulnerable range. F5 recommends updating immediately or disabling HTTP\/2 on affected ports, which blocks the two most severe flaws but not Xint\u2019s other findings \u2014 CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425 \u2014 which are in other components.<\/p>\n<p class=\"wp-block-paragraph\">The CVE-2026-123007 flaw was reported to F5 by researchers from <a href=\"https:\/\/www.rapid7.com\/blog\/post\/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed\/\">Rapid7<\/a>, <a href=\"https:\/\/www.wiz.io\/blog\/nginx-http2-rce-vulnerabilities\">Wiz<\/a>, Xint, and <a href=\"https:\/\/x.com\/ikotas00\/status\/2123071157083754677\">Ikotas Labs<\/a>, while CVE-2026-123633, dubbed Drainbreak, was discovered and reported by researchers from <a href=\"https:\/\/metnir.com\/research\/drainbreak-nginx-http2\">Metnir<\/a>, Wiz, and Xint. Only Rapid7 senior principal security researcher Stephen Fewer doesn\u2019t mention AI in his write-up. The other four teams used AI agents and harnesses, with Xint\u2019s CEO Brian Pak saying that his team\u2019s platform scanned \u201c50,000 lines of code in just 90 minutes\u201d to surface \u201ca critical vulnerability that gave an unauthenticated user a RCE path \u2014 essentially an internet breaker.\u201d<\/p>\n<h2 class=\"wp-block-heading\">Exploitation is likely<\/h2>\n<p class=\"wp-block-paragraph\">No one has exploited either flaw in the wild yet, according to the US Cybersecurity and Infrastructure Security Agency\u2019s assessment of both CVEs, but every research team built working exploits, and two describe the flaws as readily exploitable.<\/p>\n<p class=\"wp-block-paragraph\">Xint called CVE-2026-123007 highly exploitable, saying an externally reachable TLS\/HTTP\/2 port was enough to corrupt the send window, disclose addresses, and execute commands, and validated the attack over public IPs on AWS, GCP, and Azure under concurrent traffic.<\/p>\n<p class=\"wp-block-paragraph\">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.<\/p>\n<p class=\"wp-block-paragraph\">Rapid7\u2019s 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.<\/p>\n<p>\u201cExploitation 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,\u201d Yordan Ganchev, principal threat intelligence specialist at watchTowr, told CSO. \u201cMemory 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.\u201d<\/p>\n<h2 class=\"wp-block-heading\">Patch and check what you\u2019re actually running<\/h2>\n<p class=\"wp-block-paragraph\">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.<\/p>\n<p class=\"wp-block-paragraph\">Disabling HTTP\/2 comes with costs, as services that depend on it, such as native gRPC, stop working. Xint\u2019s other three flaws require specific configurations. The resolver flaw affects setups that pick their backend per request and use the mirror directive, the HTTP\/3 flaw affects QUIC listeners, and the mail proxy flaw affects deployments that use proxy on with auth_http. Xint published per-flaw mitigations in its technical write-up.<\/p>\n<p>For the accompanying Linux flaw, until a kernel patch is released, administrators who don\u2019t use SCTP can block the module from loading by adding install sctp \/bin\/false to a file under \/etc\/modprobe.d.<\/p>\n<p>Administrators should also investigate unexpected Nginx worker crashes or commands launched by Nginx workers, Wiz noted.<\/p>\n<p class=\"wp-block-paragraph\">\u201cThe real risk with this nginx bug isn\u2019t the 11 years it went unnoticed, it\u2019s how many teams will think they\u2019ve patched when they haven\u2019t,\u201d Daniel Shechter, co-founder and CEO of Miggo Security, told CSO. \u201cThe version number can be wrong because distros backport fixes without changing it, a reload doesn\u2019t swap out the running code, and the attack happens in HTTP\/2 traffic that WAFs and access logs never see. If you can\u2019t prove the fix is actually running, assume you\u2019re still exposed.\u201d<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Nginx, the web server estimated to power a third of the internet, has shipped fixes for multiple vulnerabilities, including a critical unauthenticated remote code execution flaw that puts millions of websites at risk and has existed in the code for over a decade. Researchers from several security firms independently found some of the same flaws [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":10461,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-10460","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-education"],"_links":{"self":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/10460"}],"collection":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=10460"}],"version-history":[{"count":0,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/10460\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/media\/10461"}],"wp:attachment":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=10460"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=10460"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=10460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}