F5 patches 10 open-source NGINX vulnerabilities
F5 issued emergency patches for 10 vulnerabilities in open-source NGINX, including two critical flaws that can allow unauthenticated remote code execution when HTTP/2 is enabled. The Register reported that researchers used AI assistance to uncover the flaws.
Key takeaways · 4
- 01
Check whether affected NGINX servers have HTTP/2 enabled, since that is required for the two remote-code-execution flaws.
- 02
Update open-source NGINX to version 1.31.9 or 1.30.7 to address the two HTTP/2 flaws.
- 03
If updating is not immediately possible, assess the impact of disabling HTTP/2 on affected ports, including any native gRPC dependencies.
- 04
For NGINX Plus, F5 recommends version 37.3.0.1 on the newer release line or 37.0.8.1 on the 37.0 line.
What F5 patched
F5 maintains the open-source version of NGINX, which handles HTTPS requests and routes incoming traffic to applications or APIs.[1] The Register reported that F5 issued emergency patches for 10 vulnerabilities.[1] NGINX powers about one-third of websites, or around 225 million sites, according to The Register.[1] The NGINX 1.31.9 release is dated November 18, 2026, the same date The Register published its report.[1][2] The scale of NGINX use makes checking deployed versions a practical priority for teams responsible for internet-facing services.
Two critical HTTP/2 flaws
Two of the vulnerabilities allow unauthenticated remote code execution against NGINX servers, but only when HTTP/2 is enabled on the affected server.[1] Both received a critical CVSS rating of 9.2.[1] CVE-2026-123007 affects NGINX releases dating back to version 1.9.5 in 2015.[1] CVE-2026-123633 is a use-after-free flaw affecting releases 1.19.7 through 1.31.8.[3] The findings make both protocol configuration and exact software version relevant to triage.
Updates and mitigation trade-offs
The two HTTP/2 vulnerabilities are fixed in NGINX versions 1.31.9 and 1.30.7.[3] F5 recommends updating immediately or disabling HTTP/2 on affected ports; disabling the protocol blocks the two most severe flaws, but does not address Xint's other findings.[3] That workaround also has a service impact: disabling HTTP/2 can disrupt services that depend on it, including native gRPC.[3] NGINX Plus users should update to version 37.3.0.1 on the newer release line or 37.0.8.1 on the 37.0 line.[3] Releases R33 through R36 will not receive a fix because they have reached end of technical support.[3]
Research and exposure picture
The Register reported that researchers used AI assistance to uncover the NGINX flaws; security shops named earlier in its report independently found at least one of the two CVEs and reported it to F5.[1] Xint says it found a separate Linux kernel vulnerability that can be chained with any of its five NGINX flaws to gain root privileges on the host.[4] Xint also says a chain escaped a Docker container running NGINX and obtained root on the underlying host.[4] The Register reported no evidence of active exploitation in the wild at that time.[1] Rapid7 published a proof of concept for unauthenticated remote code execution against a vulnerable Docker image running NGINX 1.31.8.[1]
The immediate decision is not just whether to patch, but whether a temporary HTTP/2 shutdown would interrupt dependent services. Teams should inventory NGINX versions and protocol settings, then coordinate remediation with owners of affected applications.
Why it matters
AI training for your team
kju.ai is built for teams: daily sessions, team analytics, and rollout support for your organization.
How this developed
19 November 2026
F5 patches 10 open-source NGINX vulnerabilities
Sources
- AI found more critical bugs in another widely used technology running 225M websitestheregister.com
- nginx.orgnginx.org
- AI unearths ‘internet breaker’ flaws in Nginx web server | CSO Onlinecsoonline.com
- NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching - Xint Blog | Insights from Offensive Security Researchersxint.io
