
Illustration
Developments3 min read
F5 patches critical NGINX HTTP/2 flaws found partly by AI scanners
F5 released NGINX 1.30.7 and 1.31.9 on 18 November, fixing six vulnerabilities according to the security advisories on nginx.org, including two in the HTTP/2 module. Security firm Wiz rates both at 9.2 out of 10 and says it found them with an AI-powered code scanner.
Key facts
- F5 released NGINX 1.30.7 and 1.31.9 on 18 November 2026, fixing six vulnerabilities according to nginx.org.
- The HTTP/2 flaw CVE-2026-123007 affects versions 1.9.5 to 1.31.8, according to nginx.org; Wiz rates it CVSS 9.2.
- According to Xint, 98.9% of 11.94m NGINX hosts with a visible version were in the affected range on 10 November.
Researched and written with AI, to Luigi's brief, positions and editorial rules. Automatically checked against the sources. How I work →
Almost every older release is affected. CVE-2026-123007, a memory corruption bug in HTTP/2 flow control, is present in versions 1.9.5 to 1.31.8, according to nginx.org, meaning code dating back to 2015. The second HTTP/2 flaw, CVE-2026-123633, affects versions from 1.19.7. Both are fixed in 1.30.7 (stable) and 1.31.9 (mainline), and in NGINX Plus 37.0.8.1 and 37.3.0.1, according to Wiz.
The severity ratings differ. F5 lists CVE-2026-123007 as “major” on nginx.org and CVE-2026-123633 only as “medium”. Wiz scores both at 9.2 under CVSS 4.0 and says it achieved remote code execution in lab tests against the official 1.31.7 and 1.31.8 builds. It has not released its exploits.
How AI found the NGINX flaws
Five teams, including Wiz, Rapid7 and Xint, reported the bugs to F5 independently, Wiz wrote. The company said it found them with Wiz Atlas, the system behind its AI code scanning product, and then used Gemini 4 Carbon and ChatGPT 5.6 Sol to confirm their impact. Xint said one of its researchers found CVE-2026-123007 on 11 October while preparing for the ZeroDay Cloud 2026 hacking contest, and that a fully automated Xint scan found four more flaws a few days later without human guidance.
How many servers are exposed is unclear. Xint counted 56.7m NGINX hosts on the Shodan search engine on 10 November. Of the 11.94m showing a version number, 98.9% fell in the affected range. That does not prove they are vulnerable, Xint cautioned, because an attack needs HTTP/2 enabled and Linux distributions often backport fixes into older packages. Neither Wiz nor Xint reports exploitation in the wild so far.
Update NGINX or switch off HTTP/2
Wiz advises upgrading as soon as possible. Where that is not immediately possible, it recommends disabling HTTP/2 for now: on version 1.25.1 or later, set “http2 off;” in the affected server block, remove the http2 parameter from the listen directive and reload NGINX. A CDN or web application firewall that terminates HTTP/2 itself may partly block attacks. Exploitation is difficult, according to Wiz, because an attacker first has to leak memory addresses and groom the heap.
The disclosure lands in a week when AI-found bugs are adding to the patching workload. On Tuesday the US agency CISA warned about Java4Shell, a Java flaw found with Codex, and US intelligence chief Jay Clayton blamed several large outages on rushed patches.
Analysis
NGINX runs behind more than 225 million websites, according to a Netcraft survey cited by Wiz. Many of them are landing pages, shops and campaign microsites run by an agency or a hosting provider, where nobody in marketing knows the version number. The pattern repeats: AI makes finding bugs cheap; fixing them still stalls on unclear ownership. Five teams found the same flaws at almost the same time, so whoever finds a bug today is rarely the only one. The same goes for attackers, which shortens the window between discovery and exploitation.
Marketing teams do not need to maintain servers themselves, but the responsibility stays in-house. Companies whose sites run with outside providers should ask in writing this week which NGINX version is live, whether HTTP/2 is on, whether a CDN sits in front and when the update will land. After the outages of the past few days, the list should also cover whether forms and tracking are tested after the restart and who is allowed to roll back, especially before Black Friday on 27 November. The recent attack via Optimizely's A/B testing script showed how quickly a marketing script can become a way in; for building a list of owners, see the report on OpenAI Daybreak.
Got AI news? Submit news →
FAQ
Which NGINX version fixes the HTTP/2 flaws?
NGINX 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026. For NGINX Plus, Wiz lists versions 37.0.8.1 and 37.3.0.1.
What if an immediate update is not possible?
Wiz recommends disabling HTTP/2 temporarily: on 1.25.1 or later, set “http2 off;” in the server block, remove the http2 parameter from listen and reload NGINX.
Are the NGINX flaws being exploited?
Neither Wiz nor Xint reported attacks as of 18 November 2026. Wiz has not published its exploits and describes exploitation as difficult.
Source
nginx.org: nginx security advisories
More sources
- Wiz Research – Blog vom 18.11.2026: CVSS 9.2, Fund mit Wiz Atlas, Prüfung mit Gemini 4 Carbon und ChatGPT 5.6 Sol, Workaround http2 off.
- Xint – Blog vom 18.11.2026: automatischer Scan fand vier Lücken, Shodan-Zahlen vom 10.11.2026.
- Forbes – Hinweisgeber, Bericht vom 18.11.2026.



