Thursday, 19 November 2026, story 3 of 7
F5 patches two critical NGINX remote code execution flaws
Both bugs sit in HTTP/2 handling and score 9.2, Wiz says; one reaches back to NGINX 1.9.5 and works in default HTTP/2 setups.

What happened
F5 shipped NGINX security updates on November 18 for two critical, unauthenticated remote code execution flaws, CVE-2026-123633 and CVE-2026-123007, according to Wiz Research. Both need HTTP/2 enabled and carry a CVSS 4.0 score of 9.2. Wiz says CVE-2026-123007 affects versions 1.9.5 through 1.31.8 and worked against a server serving only static files. CVE-2026-123633 affects 1.19.7 through 1.31.8 and applies to reverse-proxy setups.
Wiz lists fixed releases: NGINX OSS 1.30.7 stable and 1.31.9 mainline, plus separate NGINX Plus builds. Disabling HTTP/2 is the stopgap. The release also fixes eight other CVEs.
What it means
The exposure test is simple: NGINX with HTTP/2 enabled. The affected version ranges are wide, so many long-running deployments are likely in scope. Wiz stresses that secure application code does not help, and that ASLR does not stop these bugs. One NGINX instance often fronts several apps or APIs, so one unpatched edge server can expose all of them.
The source reports no exploitation in the wild, but it does say the gap between disclosure and exploitation may shrink. That is Wiz's view, and it sells AI code scanning. Five teams finding the same bugs independently lends it some weight. Three other 9.2 flaws in the release, in HTTP/3, the DNS resolver and the mail proxy, only matter if those features are configured. Check for them too.
What to do: Inventory NGINX instances with HTTP/2 enabled today, upgrade to a fixed release (1.30.7 stable, 1.31.9 mainline), and turn HTTP/2 off temporarily where you cannot.
Source
Filed under Safety and security. Published .
"What it means" is analysis, not reporting. Found an error? Write to daily@vibitely.com.