SafetyPublished All news from that day
Ongoing case: Cyber-capable AI models 32 storiesnginx 1.30.7 and 1.31.9 fix two HTTP/2 flaws Wiz rates Critical
Wiz says its Wiz Atlas AI harness found both flaws, which it says allow unauthenticated code execution when HTTP/2 is on; the 1.31.9 release fixes ten vulnerabilities.
Check our sources · 15 facts from 4 sourcesAnyone running nginx with HTTP/2 enabled should upgrade to 1.30.7 (stable) or 1.31.9 (mainline). The nginx project released 1.31.9 on GitHub on 18 November 2026 with fixes for ten vulnerabilities, including two HTTP/2 flaws that Wiz Research rates Critical. The 18 November date is for 1.31.9 only; nginx's advisory page lists 1.30.7 as a fixed version.
The two flaws are CVE-2026-123633, a use-after-free in HTTP/2, and CVE-2026-123007, a memory-corruption bug in HTTP/2 flow control. nginx's own advisory page rates the second "major" and the first "medium", and lists vulnerable versions from 1.9.5 and from 1.19.7 up to 1.31.8. Wiz scores both 9.2 under CVSS 4.0 and says they allow unauthenticated remote code execution; the two ratings use different scales.
Wiz says both flaws need HTTP/2 enabled, and that it demonstrated code execution on nginx serving ordinary static files, with no backend application or third-party modules. It says it confirmed code execution on official nginx 1.31.7 and 1.31.8 builds. Wiz says the older flaw dates to nginx 1.9.5 in 2015 and the other has been there for nearly six years.
Wiz says it built working proof-of-concept exploits for lab setups and will not release them, and its post does not say the flaws are being exploited. Wiz also says Ikotas Labs, Metnir, Rapid7 and Xint reported the same issues independently. CISA's Known Exploited Vulnerabilities catalogue, in the feed released on 17 November 2026 at 17:53 UTC, does not list either flaw; that feed predates the 18 November release.
Operators who cannot upgrade at once can set "http2 off;" in affected server blocks on nginx 1.25.1 or later and remove the http2 parameter from listen directives, then reload. Wiz says it used its Wiz Atlas AI code-scanning harness to find both flaws and Gemini 4 Carbon and ChatGPT 5.6 Sol to validate their impact. Wiz also says nginx powers more than 225 million websites.
Underlined sentences link to the facts we checked. Dotted words open a short explainer.
Fact 11 of 15 · from Wiz, 18 Nov 2026
If you cannot upgrade immediately, temporarily disable HTTP/2 on affected NGINX instances: Set http2 off; in affected server blocks on NGINX 1.25.1 or later, and remove the http2 parameter from any listen directives . Test application compatibility, reload NGINX , and confirm the old workers have exited.
Your reaction
We count reactions per story and day, never who reacted. The counts help us choose what goes in the monthly issue. If you are signed in, your own page shows yours too.
We count reactions per story and day, never who reacted. They help choose what goes in the monthly issue.
Check our sources
Every sentence above is checked against these 4 sources.
1 nginx release 1.31.9
Open the source-
The nginx project released nginx 1.31.9 mainline on GitHub on 18 November 2026 with fixes for ten vulnerabilities.
Toned down to what the source says
citepluknet released this 18 Nov 15:54 ... nginx-1.31.9 mainline version has been released, with vulnerability fixes for use-after-free in resolver (CVE-2026-123634), memory corruption in HTTP/2 flow control (CVE-2026-123007), ... and insufficient validation in stream ssl_preread module (CVE-2026-123640).
-
The nginx 1.31.9 release lists fixes for CVE-2026-123007 (memory corruption in HTTP/2 flow control) and CVE-2026-123633 (use-after-free in HTTP/2), among ten CVEs.
citenginx-1.31.9 mainline version has been released, with vulnerability fixes for ... memory corruption in HTTP/2 flow control (CVE-2026-123007), use-after-free in HTTP/3 (CVE-2026-121810), use-after-free in HTTP/2 (CVE-2026-123633), ...
2 nginx security advisories
Open the source-
nginx.org's security advisories page lists CVE-2026-123007 as severity "major" with vulnerable versions 1.9.5 to 1.31.8, and CVE-2026-123633 as severity "medium" with vulnerable versions 1.19.7 to 1.31.8; both are not vulnerable in 1.31.9 and later or 1.30.7 and later.
cite
3 Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007
Open the source-
Wiz says both CVE-2026-123633 and CVE-2026-123007 are rated Critical, with a CVSS 4.0 score of 9.2, and are unauthenticated remote code execution vulnerabilities in NGINX.
citeThe vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2. ... two critical unauthenticated remote code execution vulnerabilities in NGINX
-
Wiz says both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server.
citeBoth vulnerabilities require HTTP/2 to be enabled on the affected NGINX server.
-
Wiz says its testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.
citeOur testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.
-
Wiz says it confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds.
citeWe confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds.
-
Wiz says the integer underflow vulnerability dates back to NGINX 1.9.5 in 2015 and the use-after-free vulnerability had been there for nearly six years.
citeThe integer underflow vulnerability dates back to NGINX 1.9.5 in 2015, meaning it had been hiding in the code for more than a decade. The use-after-free vulnerability had been there for nearly six years.
-
Wiz says it built proof-of-concept exploits and ran them in multiple lab settings against servers running common NGINX configurations, and that it will not be releasing them at this time.
citebuilt proof-of-concept exploits and managed to run them in multiple lab settings against servers running common NGINX configurations we've seen in customer environments. In the interest of customer protection, we will not be releasing these exploits at this time.
-
Wiz says Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint independently uncovered the vulnerabilities and reported them to F5, the company behind NGINX.
citeWiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered CVE-2026-123633 and CVE-2026-123007, two critical unauthenticated remote code execution vulnerabilities in NGINX, and reported them to F5, the company behind NGINX.
-
Wiz says that if you cannot upgrade immediately you can set http2 off; in affected server blocks on NGINX 1.25.1 or later, remove the http2 parameter from listen directives, reload NGINX and confirm the old workers have exited.
citeIf you cannot upgrade immediately, temporarily disable HTTP/2 on affected NGINX instances: Set http2 off; in affected server blocks on NGINX 1.25.1 or later, and remove the http2 parameter from any listen directives . Test application compatibility, reload NGINX , and confirm the old workers have exited.
-
Wiz says it used Wiz Atlas, the harness powering its AI Code scanning solution, to discover both vulnerabilities, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate their impact.
citeWiz Research used Wiz Atlas , the harness powering Wiz's AI Code scanning solution , to discover both vulnerabilities. Our researchers used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate the impact of both vulnerabilities
-
Wiz describes NGINX as the world's most widely used open-source web server and says it powers more than 225 million websites.
citeAs the world's most widely used open-source web server , it powers more than 225 million websites .
-
Wiz's disclosure timeline says it reported the use-after-free to F5 on 21 October 2026 and the second flaw on 16 November 2026, and that F5's security release and coordinated public disclosure came on 18 November 2026.
citeOctober 21, 2026: Wiz reports the HTTP/2 use-after-free vulnerability, later assigned CVE-2026-123633, to F5 ... November 16, 2026 : Wiz reports the second HTTP/2 vulnerability, later assigned CVE-2026-123007, to F5. ... November 18, 2026: F5 security release and coordinated public disclosure.
4 CISA Known Exploited Vulnerabilities catalog (JSON feed)
Open the source archived copy-
CISA's Known Exploited Vulnerabilities catalog, in the JSON feed released 17 November 2026 at 17:53 UTC, which predates the nginx release of 18 November, does not list CVE-2026-123007 or CVE-2026-123633.
cite
Every sentence above is checked against these 4 sources. Each fact has its own address you can cite.
Source 1 · nginx (GitHub) · 18 Nov 2026
nginx release 1.31.9
The nginx project released nginx 1.31.9 mainline on GitHub on 18 November 2026 with fixes for ten vulnerabilities.
Toned down to what the source sayspluknet released this 18 Nov 15:54 ... nginx-1.31.9 mainline version has been released, with vulnerability fixes for use-after-free in resolver (CVE-2026-123634), memory corruption in HTTP/2 flow control (CVE-2026-123007), ... and insufficient validation in stream ssl_preread module (CVE-2026-123640).
The nginx 1.31.9 release lists fixes for CVE-2026-123007 (memory corruption in HTTP/2 flow control) and CVE-2026-123633 (use-after-free in HTTP/2), among ten CVEs.
nginx-1.31.9 mainline version has been released, with vulnerability fixes for ... memory corruption in HTTP/2 flow control (CVE-2026-123007), use-after-free in HTTP/3 (CVE-2026-121810), use-after-free in HTTP/2 (CVE-2026-123633), ...
Source 2 · nginx.org · 18 Nov 2026
nginx security advisories
nginx.org's security advisories page lists CVE-2026-123007 as severity "major" with vulnerable versions 1.9.5 to 1.31.8, and CVE-2026-123633 as severity "medium" with vulnerable versions 1.19.7 to 1.31.8; both are not vulnerable in 1.31.9 and later or 1.30.7 and later.
Source 3 · Wiz · 18 Nov 2026
Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007
Wiz says both CVE-2026-123633 and CVE-2026-123007 are rated Critical, with a CVSS 4.0 score of 9.2, and are unauthenticated remote code execution vulnerabilities in NGINX.
The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2. ... two critical unauthenticated remote code execution vulnerabilities in NGINX
Wiz says both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server.
Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server.
Wiz says its testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.
Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.
Show all 11 factsShow fewer facts
Wiz says it confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds.
We confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds.
Wiz says the integer underflow vulnerability dates back to NGINX 1.9.5 in 2015 and the use-after-free vulnerability had been there for nearly six years.
The integer underflow vulnerability dates back to NGINX 1.9.5 in 2015, meaning it had been hiding in the code for more than a decade. The use-after-free vulnerability had been there for nearly six years.
Wiz says it built proof-of-concept exploits and ran them in multiple lab settings against servers running common NGINX configurations, and that it will not be releasing them at this time.
built proof-of-concept exploits and managed to run them in multiple lab settings against servers running common NGINX configurations we've seen in customer environments. In the interest of customer protection, we will not be releasing these exploits at this time.
Wiz says Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint independently uncovered the vulnerabilities and reported them to F5, the company behind NGINX.
Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered CVE-2026-123633 and CVE-2026-123007, two critical unauthenticated remote code execution vulnerabilities in NGINX, and reported them to F5, the company behind NGINX.
Wiz says that if you cannot upgrade immediately you can set http2 off; in affected server blocks on NGINX 1.25.1 or later, remove the http2 parameter from listen directives, reload NGINX and confirm the old workers have exited.
If you cannot upgrade immediately, temporarily disable HTTP/2 on affected NGINX instances: Set http2 off; in affected server blocks on NGINX 1.25.1 or later, and remove the http2 parameter from any listen directives . Test application compatibility, reload NGINX , and confirm the old workers have exited.
Wiz says it used Wiz Atlas, the harness powering its AI Code scanning solution, to discover both vulnerabilities, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate their impact.
Wiz Research used Wiz Atlas , the harness powering Wiz's AI Code scanning solution , to discover both vulnerabilities. Our researchers used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate the impact of both vulnerabilities
Wiz describes NGINX as the world's most widely used open-source web server and says it powers more than 225 million websites.
As the world's most widely used open-source web server , it powers more than 225 million websites .
Wiz's disclosure timeline says it reported the use-after-free to F5 on 21 October 2026 and the second flaw on 16 November 2026, and that F5's security release and coordinated public disclosure came on 18 November 2026.
October 21, 2026: Wiz reports the HTTP/2 use-after-free vulnerability, later assigned CVE-2026-123633, to F5 ... November 16, 2026 : Wiz reports the second HTTP/2 vulnerability, later assigned CVE-2026-123007, to F5. ... November 18, 2026: F5 security release and coordinated public disclosure.
Source 4 · CISA · 21 Oct 2026
CISA Known Exploited Vulnerabilities catalog (JSON feed)
CISA's Known Exploited Vulnerabilities catalog, in the JSON feed released 17 November 2026 at 17:53 UTC, which predates the nginx release of 18 November, does not list CVE-2026-123007 or CVE-2026-123633.
Topics
The morning email
On the mornings we publish: the three top stories and up to four short ones. Free.
We email you a link to confirm. An issue may include one sponsor, always labelled Sponsored · Advertisement. Our emails count opens and clicks, not who made them. Unsubscribe in one click. What we keep
