{"id":62952,"date":"2026-11-20T00:35:05","date_gmt":"2026-11-19T21:35:05","guid":{"rendered":"https:\/\/infolight.ua\/2026\/11\/20\/decade-old-hole-in-nginx-five-critical-flaws\/"},"modified":"2026-11-20T00:35:05","modified_gmt":"2026-11-19T21:35:05","slug":"decade-old-hole-in-nginx-five-critical-flaws","status":"publish","type":"post","link":"https:\/\/infolight.ua\/en\/2026\/11\/20\/decade-old-hole-in-nginx-five-critical-flaws\/","title":{"rendered":"Decade-old hole in nginx: five critical flaws let attackers hijack servers without a password"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Security researchers have found five critical vulnerabilities in <strong>nginx<\/strong>, the software that serves web pages for a large share of the world\u2019s websites. They let an attacker run code on a server without a login or password, and, chained with a still unpatched Linux kernel bug, take full control of it. The most dangerous of the flaws has been in the nginx code <strong>since 2015<\/strong>, so administrators should update without delay.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The vulnerabilities were found by <strong><a href=\"https:\/\/xint.io\/blog\/nginx2root-remote-code-execution\">Xint<\/a><\/strong> (part of Theori), which named the series nginx2root and published attack demos on a dedicated site, <a href=\"https:\/\/nginx2root.com\/\">nginx2root.com<\/a>. On 18 November <strong>F5<\/strong>, which owns nginx, released fixed versions and <a href=\"https:\/\/my.f5.com\/manage\/s\/article\/K000164058\">security advisory K000164058<\/a>. The same day the EU\u2019s Computer Emergency Response Team, <a href=\"https:\/\/cert.europa.eu\/publications\/security-advisories\/2026-022\/\">CERT-EU<\/a>, issued a warning.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">\u201cIt is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances,\u201d CERT-EU said.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Why almost every website is concerned<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">nginx is the most widely used web server in the world. According to <a href=\"https:\/\/w3techs.com\/technologies\/details\/ws-nginx\">W3Techs<\/a>, it runs about <strong>a third of all websites<\/strong> whose server can be identified. It is used both as the main server and as the \u201cfront door\u201d for applications, in Docker images and Kubernetes clusters.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The main flaw, <strong>CVE-2026-123007<\/strong>, is a bug in how nginx handles HTTP\/2 flow control. It arrived in version 1.9.5, released on 22 September 2015 together with HTTP\/2 support itself, and is present in every official release up to 1.31.8. Wiz, which found the bug independently, showed that the attack works even against a server that only serves static files, with no application or third-party modules, <a href=\"https:\/\/www.securityweek.com\/f5-patches-critical-nginx2root-flaws-as-poc-exploits-go-public\/\">SecurityWeek<\/a> reports.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Internet-wide scans show the scale. Using Shodan, Xint counted <strong>56.7 million<\/strong> nginx hosts; of those that reveal their version, <strong>98.9%<\/strong> fall within the vulnerable range. Censys found about <strong>9 million<\/strong> Internet-facing nginx servers with an affected version and HTTP\/2 enabled. That does not mean all of them are vulnerable: Ubuntu, Debian and other distributions often patch packages without changing the version number.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1920\" height=\"1080\" src=\"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en.png\" alt=\"Diagram of the nginx2root attack: from an Internet request through the HTTP\/2 flaw and a Linux kernel bug to root on the server, and where the chain can be broken\" class=\"wp-image-62947\" srcset=\"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en.png 1920w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en-1000x563.png 1000w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en-1500x844.png 1500w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en-768x432.png 768w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-attack-chain-en-1536x864.png 1536w\" sizes=\"auto, (max-width: 1920px) 100vw, 1920px\" \/><\/a><figcaption class=\"wp-element-caption\">How the nginx2root chain works and where to break it. Diagram: InfoLight.UA based on Xint, F5, Rapid7, CERT-EU<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What attackers can do<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">All five flaws allow code execution with the privileges of the <strong>nginx worker process<\/strong>, the one that serves visitors\u2019 requests. It usually does not run as root. F5 rated each of them <strong>9.2 out of 10<\/strong> on the CVSS 4.0 scale.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To gain full control, Xint chained nginx2root with a separate bug in the Linux kernel\u2019s SCTP module that dates back to 2018. This gave the researchers root on the host, including by breaking out of a Docker container. No kernel fix was available when the report was published.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Vulnerability<\/th><th>Where the bug is<\/th><th>When a server is exposed<\/th><\/tr><\/thead><tbody><tr><td><strong>CVE-2026-123007<\/strong><\/td><td>HTTP\/2 flow control<\/td><td>HTTP\/2 enabled<\/td><\/tr><tr><td><strong>CVE-2026-123633<\/strong><\/td><td>HTTP\/2 combined with upstream proxying<\/td><td>HTTP\/2 enabled, nginx used as a proxy<\/td><\/tr><tr><td><strong>CVE-2026-121810<\/strong><\/td><td>HTTP\/3 (QUIC)<\/td><td>HTTP\/3 enabled, nginx used as a proxy<\/td><\/tr><tr><td><strong>CVE-2026-123634<\/strong><\/td><td>DNS resolver<\/td><td>proxy_pass built from variables, together with mirror or SSI<\/td><\/tr><tr><td><strong>CVE-2026-113425<\/strong><\/td><td>Mail proxy (auth_http)<\/td><td>nginx used as a mail proxy<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\">The five nginx2root vulnerabilities. Sources: Xint, CERT-EU<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How real the threat is right now<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Exploitation is made harder by ASLR, a protection that randomises where data sits in memory: according to F5, code execution is only possible if it is disabled or bypassed. Rapid7 and Wiz, however, bypassed ASLR in their tests.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rapid7\u2019s public exploit needs to send the server about <strong>128 GB<\/strong> of HTTP\/2 traffic and works on x86-64 processors with a specific instruction set. On links slower than roughly 300 Mbit\/s, the attack cannot finish within nginx\u2019s default one-hour connection limit, according to <a href=\"https:\/\/thehackernews.com\/2026\/11\/10-year-old-nginx-http2-flaw-lets.html\">The Hacker News<\/a>. Censys, however, published another PoC on GitHub that does not need such traffic volumes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">No attacks in the wild have been reported so far, and as of 19 November nginx2root was not in the US CISA catalogue of known exploited vulnerabilities (KEV). But working attack code is already public, so the window for a calm update is closing fast.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1920\" height=\"1080\" src=\"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en.png\" alt=\"nginx2root timeline: from the release of nginx 1.9.5 in September 2015 to the fixes and warnings in November 2026\" class=\"wp-image-62949\" srcset=\"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en.png 1920w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en-1000x563.png 1000w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en-1500x844.png 1500w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en-768x432.png 768w, https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-timeline-en-1536x864.png 1536w\" sizes=\"auto, (max-width: 1920px) 100vw, 1920px\" \/><\/a><figcaption class=\"wp-element-caption\">nginx2root timeline. Infographic: InfoLight.UA based on Xint, F5, CERT-EU, The Hacker News<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What administrators should do<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Update nginx<\/strong> to 1.30.7 (stable) or 1.31.9 (mainline). For NGINX Plus, to 37.0.8.1 or 37.3.0.1. Official Docker images with these versions are already available.<\/li>\n\n\n\n<li><strong>Fully restart nginx.<\/strong> A reload does not replace the running executable, and existing HTTP\/2 connections stay alive.<\/li>\n\n\n\n<li><strong>Check the package version against your distribution\u2019s advisory<\/strong> if nginx comes from the Ubuntu, Debian or another repository: <code>nginx -v<\/code> may show the old version even after a fix. As of 18 November, Ubuntu and Debian had not yet shipped fixed packages.<\/li>\n\n\n\n<li><strong>If you cannot update immediately<\/strong>, temporarily disable HTTP\/2 (this closes two of the five flaws) and HTTP\/3, restrict mail ports to trusted networks, and avoid building proxy_pass addresses from variables together with mirror or SSI.<\/li>\n\n\n\n<li><strong>Block the SCTP module<\/strong> on servers that do not use it: add the line <code>install sctp \/bin\/false<\/code> to a .conf file in \/etc\/modprobe.d\/. This does not unload a module that is already loaded.<\/li>\n\n\n\n<li><strong>Look for signs of attack:<\/strong> \u201cworker process \u2026 exited on signal\u201d entries in the error log, unusual processes running as the nginx user, and long-lived HTTP\/2 connections with heavy inbound traffic but few requests in the access log.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">To check whether a server answers over HTTP\/2 from the Internet, run <code>openssl s_client -connect your-site:443 -alpn h2<\/code>: the line \u201cALPN protocol: h2\u201d means HTTP\/2 is enabled. Detailed guidance on checks and temporary mitigations is in the <a href=\"https:\/\/xint.io\/blog\/nginx2root-remote-code-execution\">Xint report<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is not the first critical nginx flaw this year: in May F5 fixed CVE-2026-42945, which affected versions 0.6.27 to 1.30.0, as <a href=\"https:\/\/www.ncsc.govt.nz\/alerts\/cve-2026-42945-affecting-nginx\/\">New Zealand\u2019s NCSC<\/a> reported. Regular web server updates are not a formality but basic hygiene for anyone who runs a website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Photo: <a href=\"https:\/\/commons.wikimedia.org\/wiki\/File:CERN_Computer_Center_02.jpg\">SimonWaldherr \/ Wikimedia Commons<\/a>, <a href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/4.0\/\">CC BY-SA 4.0<\/a>. Diagram and infographic: InfoLight.UA.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Xint researchers found five nginx flaws that allow code execution on a server without authentication. A fix is out \u2013 here is who is affected and what to do.<\/p>\n","protected":false},"author":25,"featured_media":62941,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"wds_primary_category":1690,"footnotes":""},"categories":[1279,1690,1307],"tags":[],"class_list":["post-62952","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-information-security","category-neus","category-technology"],"jetpack_featured_media_url":"https:\/\/infolight.ua\/wp-content\/uploads\/2026\/11\/nginx2root-servery-cern.jpg","_links":{"self":[{"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/posts\/62952","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/comments?post=62952"}],"version-history":[{"count":0,"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/posts\/62952\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/media\/62941"}],"wp:attachment":[{"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/media?parent=62952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/categories?post=62952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/infolight.ua\/en\/wp-json\/wp\/v2\/tags?post=62952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}