NGINX fixes ten flaws: why African services must verify HTTP/2 exposure
NGINX software, used as a web server and reverse proxy, fixes ten vulnerabilities in versions 1.30.7 and 1.31.9. They affect Hypertext Transfer Protocol (HTTP) processing, Transport Layer Security (TLS) and several modules. No public exploitation was established by 21 November.
Severity
4Affected country
ZASector
Technology & cloudPublished
21 November 2026
Our score measures operational relevance to Africa — not the global virality of the story.

Contents · 6
Ten fixes released on 18 November
NGINX released 1.30.7 stable and 1.31.9 mainline on 18 November 2026, fixing ten vulnerabilities. The set affects HTTP/2, HTTP/3, TLS 1.3, DNS resolution, mail proxying, the PROXY protocol and selected configuration directives. CERT-EU recommends rapid updates for Internet-facing instances.
The most prominent issue, CVE-2026-123007, is memory corruption in HTTP/2 flow control. F5 says crafted traffic can cause a flow-control window to exceed its threshold, resulting in a heap overflow and normally a worker crash. Code execution is considered possible where ASLR is disabled or can be bypassed. The flaw is in the data plane, not the management interface.
Researchers have demonstrated the issue, but CERT-EU said no exploitation in the wild had been reported when it published its 18 November advisory. That distinction must be preserved: an urgent patch does not justify announcing an active campaign without evidence. It does mean defenders can no longer treat the issue as purely theoretical.
HTTP/2 is only part of the release
CVE-2026-123633 is a use-after-free in HTTP/2 when connection draining closes an active connection while NGINX connects to an upstream. CVE-2026-121810 affects HTTP/3. CVE-2026-118899 can trigger an infinite loop while reading a request body over TLS 1.3.
Other references affect the resolver, mail proxy module, PROXY protocol version 2, an alias and try_files combination, client-certificate validation in the stream module and ssl_preread. Not every installation loads these modules or configurations. Conversely, a team may use NGINX indirectly through a Kubernetes ingress controller, appliance, API gateway or security product without listing it among ordinary Linux servers.
The upstream non-vulnerable releases are 1.30.7 and 1.31.9 or later. Linux distributions may backport fixes into their own revisions, so validation must use the package vendor’s advisory rather than compare a banner mechanically with upstream numbering. Integrated products may follow separate fixed-version schedules from their vendors.
Why this matters directly to Africa
NGINX commonly fronts web services, mobile APIs, payment platforms, health applications, public portals and supplier consoles. It terminates TLS, distributes requests and hides internal servers. A worker failure can create visible downtime; exploitable memory corruption may become an entry point into the application environment.
HTTP/2 is especially common for African mobile-oriented services because it can reduce connection overhead and improve loading over high-latency networks. Disabling it abruptly as an emergency measure may degrade performance and increase data use. A tested upgrade is normally preferable unless a fixed build is unavailable.
Multi-country architectures create another blind spot. The primary domain may sit behind an updated CDN while a partner API, staging system, regional entry point or direct origin address retains vulnerable code. Inventory must follow real traffic, certificates, load-balancer configurations and clusters rather than the public homepage alone.
Patching without avoidable disruption
NGINX normally supports graceful reload, but a binary update still requires evidence that old workers have exited. In containers, teams need to rebuild or obtain a fixed image, verify its digest, replace pods and ensure the old ReplicaSet no longer receives traffic. Kubernetes ingress controllers and related images may have separate support matrices.
Before maintenance, preserve access and error logs, worker-restart metrics, segmentation-fault records and orchestrator events. A rise in unusual HTTP/2 connections or dying workers warrants investigation, but does not alone prove exploitation of a specific CVE. Application defects, legitimate load and other bugs can produce similar symptoms.
After the update, teams should test HTTP/1.1, HTTP/2 and, where enabled, HTTP/3; uploads; long-lived connections; upstream proxying; TLS termination; WAF rules; and failure behaviour when a backend is unavailable. A single HTTP 200 from the homepage does not exercise affected paths.
Evidence to request from hosting and integration providers
Many African small businesses, public bodies and associations do not administer their own reverse proxy. Their provider needs to supply more than a “maintenance completed” message. Useful evidence includes:
- exact product: NGINX Open Source, NGINX Plus, ingress or embedded appliance;
- branch, vendor revision and backported CVEs;
- active modules and protocols, particularly HTTP/2 and HTTP/3;
- deployment time and proof that old workers or pods stopped;
- availability and regression-test results;
- abnormal events reviewed for the period before remediation.
A hidden banner reduces opportunistic information collection but fixes nothing. A WAF may filter selected traffic shapes without covering a protocol or memory-management defect. Segmentation, low worker privileges and ASLR reduce possible impact; they complement the update.
Configuration backup and rollback also matter. Teams should preserve the exact pre-change configuration, validate it with the corrected binary before reload, and keep a tested path back to a known-good package. Rollback must not silently restore the vulnerable build; when a functional regression blocks deployment, the safer fallback may be temporary traffic restriction or failover to a separately patched node.
An infrastructure warning, not a victim list
No reviewed source establishes that a named African service was exploited through these NGINX vulnerabilities. Africa Cyber Review therefore does not publish a list inferred from Internet banners. The value of the alert lies elsewhere: it provides versions, modules and protocols that teams can verify before possible exploitation becomes widespread.
The defensible response is to identify every NGINX termination point, prioritise Internet entry points using HTTP/2, apply 1.30.7, 1.31.9 or the vendor fix, genuinely recycle processes and preserve evidence. That discipline turns a global alert into measurable risk reduction for African services.
— ◆ —